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
This will get us to an MVP of blackbox fuzzing of Noir programs which will likely be pretty brittle. Foundry performs various tricks such as inspecting storage and constants which are referenced in the bytecode in order to improve performance. In future we'll want to do similar inspection of the generated ACIR to find interesting values and weight input generation to focus on the ranges of values around these values.
The content you are editing has changed. Please copy your edits and refresh the page.
# Description
## Problem\*
Resolves#5262
## Summary\*
This PR pulls out a bunch of relevant constants from the ACIR/brillig
bytecode so we can feed these into the fuzzer's strategy to ensure
proper coverage of these values.
## Additional Context
## Documentation\*
Check one:
- [x] No documentation needed.
- [ ] Documentation included in this PR.
- [ ] **[For Experimental Features]** Documentation to be submitted in a
separate PR.
# PR Checklist\*
- [x] I have tested the changes locally.
- [x] I have formatted the changes with [Prettier](https://prettier.io/)
and/or `cargo fmt` on default settings.
This will get us to an MVP of blackbox fuzzing of Noir programs which will likely be pretty brittle. Foundry performs various tricks such as inspecting storage and constants which are referenced in the bytecode in order to improve performance. In future we'll want to do similar inspection of the generated ACIR to find interesting values and weight input generation to focus on the ranges of values around these values.
Improvements
The text was updated successfully, but these errors were encountered: