-
Notifications
You must be signed in to change notification settings - Fork 206
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(brillig): Handle Brillig overflow checks inside the VM #6425
Draft
vezenovm
wants to merge
2
commits into
master
Choose a base branch
from
mv/overflow-check-in-vm-brillig
base: master
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.
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
Changes to Brillig bytecode sizes
🧾 Summary (10% most significant diffs)
Full diff report 👇
|
Changes to number of Brillig opcodes executed
🧾 Summary (10% most significant diffs)
Full diff report 👇
|
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.
Description
Problem*
Part of a general effort to reduce Brillig bytecode size and execution traces
Summary*
This PR simply removes the
add_overflow_check
from brillig_gen and leaves it up to the VM to implement their own overflow checks if that is what is desired. Handling for the overflow checks done during Brillig gen was included in the Brillig VM.Additional Context
In the following flamegraphs I search for jump and jump if opcodes. The total samples went down from 126k to 99k samples.
sha256_regression
on master (126k samples, 29.5% of the program execution is jumps and jump ifs):sha256_regression
after this PR (99k samples, 25.9% of the program execution is jumps and jump ifs on a much more reduced trace):Documentation*
Check one:
PR Checklist*
cargo fmt
on default settings.