-
Notifications
You must be signed in to change notification settings - Fork 167
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
Optimize computation of DEEP queries in recursive verifier #1594
Conversation
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! (based on the fact that tests pass - didn't thoroughly check the logic)
7ae500f
to
bec35e8
Compare
Thanks for the review! |
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.
Looks good! Thank you! Not a super deep review, but I did leave some comments inline (most are very minor).
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.
All looks good! Thank you!
This is ready to be merged |
411b92c
to
b3204d6
Compare
chore: update changelog chore: address feedback Signed-off-by: Al-Kindi-0 <[email protected]>
chore: changelog update chore: add back file and update it Revert "refactor: remove file" This reverts commit 384a5af.
8d1547c
to
d586616
Compare
I have also included the changes from #1596 as it was the easiest way to get commits in that one signed |
Using better stack management, optimizes the computation of the DEEP queries by about 6%. This is less than the 10% we got in the signature verifier as the VM trace is wider and hence the impact of the optimizations is smaller.