You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 5, 2024. It is now read-only.
there is already a u16 fixed lookup inside state circuit. So maybe we can refactor codes a bit so other sub curcuits can use that?
Right, thanks for the heads up! I think u8/u16 defined in state circuit can all be reused with evm circuit (and maybe other circuit which need range check)
### Description
[_PR description_]
### Issue Link
Close#1426
Depends by
#1414
### Type of change
- [x] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
### Contents
- [x] constraint builder in evm circuit support u16 lookup
- [x] rename `byte_table` to `u8_table` and `query_byte` to `query_u8`
so it align with `query_u16` and so on in the future
- [x] refactor state circuit and evm circuit to reuse range table.
Describe the feature you would like
part of the optimisation proposed during word lo/hi refactor
Additional context
No response
cargo test -p zkevm-circuits --release get_exec_steps_occupancy --features test -- --nocapture --ignored
The text was updated successfully, but these errors were encountered: