chore: Add optimization to #4716#4718
Merged
jfecher merged 5 commits intojf/opt-array-merging2from Apr 5, 2024
Merged
Conversation
Contributor
Changes to circuit sizes
🧾 Summary (10% most significant diffs)
Full diff report 👇
|
Contributor
Author
|
Update: adding the |
Contributor
Author
|
Ah, ok. I was trying to figure out why the opt percentages on this were smaller than #4716, but they're just relative to that PR. So the 20% hashmap improvement is a further improvement on top of the 25% on the other PR. Merging this now since the additional bugs are fixed. |
This file contains hidden or 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
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*
Summary*
Adds the actual array set optimization to #4716. This is separate since the other PR still has errors and I want to fix those before adding more with the actual optimization. At the same time, I've put up this PR to see the circuit size changes in CI.
Additional Context
This PR is currently failing a few additional tests. I think these are mostly array out of bounds accesses from storing which indices were changed. In some if statements, these indices may be out of bounds but not error since that if case was not run. Trying to get and store to this same index after the if then gives an OOB error. This can be fixed by only applying the optimization when constant indices are used and filtering out the OOB ones but then dynamic indices won't see this important optimization at all.
Documentation*
Check one:
PR Checklist*
cargo fmton default settings.