-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: support go corset optimisation and metadata #713
Open
DavePearce
wants to merge
3
commits into
main
Choose a base branch
from
feat/allow-checker-to-configure-go-corset-optimisations
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
feat: support go corset optimisation and metadata #713
DavePearce
wants to merge
3
commits into
main
from
feat/allow-checker-to-configure-go-corset-optimisations
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This adds support for passing a go-corset optimisation level via the bin/checker. The purpose of this is to enable testing at different optimisation levels to see what effect this has.
This exposes the metadata stored in the zkevm.bin file, such that it can be used for cross-checking purposes. For example, the metadata includes the git commit of the enclosing repository when it was built.
31da448
to
6d90e47
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #713 +/- ##
=========================================
Coverage 68.40% 68.40%
Complexity 1185 1185
=========================================
Files 323 323
Lines 13131 13131
Branches 1319 1319
=========================================
Hits 8982 8982
Misses 3597 3597
Partials 552 552
*This pull request uses carry forward flags. Click here to find out more. |
gusiri
approved these changes
Feb 21, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR does three things:
(checker) Updates the checker to include the "full suite" when running in benchmark mode. This is relevant for testing to try and gauge total work done by the prover.
(optimisation) Adds the ability to specify the optimisation level that
go-corset
applies when compiling thezkevm.bin
file down to theair.Schema
which is then consumed by the prover. In particular, thebin/checker
is updated to allow the optimisation level to be specified on the command-line for testing purposes. ADEFAULT_OPTIMISATION_LEVEL
is provided for normal use.(metadata) Exposes the metadata map which is stored within the
zkevm.bin
file. This is a general purpose mechanism for embedding information within thezkevm.bin
file. For example, it currently includes the git commit of the enclosing repository when thezkevm.bin
file was built, and a timestamp. However, it could include other information as needed.