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
…ime (#6307)
# Description
## Problem\*
Resolves#6267
Pushing as a draft to see bytecode size regressions we get.
## Summary\*
This version for the code in #6267 took less than 2 gigs of ram and
4.66s to compile. The code on master takes ~20 gigs and 94.3s to
compile. The noir-contracts workspace with this mem2reg takes ~20 gigs
of ram and 94.3s to compile vs. >70 gigs of ram and 4.5 min to compile
w/ the mem2reg on master.
## 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.
---------
Co-authored-by: Tom French <[email protected]>
Aim
Compile programs that use this pattern:
Expected Behavior
Program should not take 20gb of ram to compile
Bug
High RAM usage during mem2reg after unrolling, and slow compilation
To Reproduce
Workaround
Yes
Workaround Description
Use the unsafe equivalent to_be_radix(256) instead of to_be_bytes()
Additional Context
No response
Project Impact
None
Blocker Context
No response
Nargo Version
No response
NoirJS Version
No response
Proving Backend Tooling & Version
No response
Would you like to submit a PR for this Issue?
None
Support Needs
No response
The text was updated successfully, but these errors were encountered: