-
Notifications
You must be signed in to change notification settings - Fork 185
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: use RAM/ROM opcode when supported by the backend #1282
Conversation
I don't understand why we are removing functionalities, using the proper opcode sooner is better than using a wrong one and changing it after. We want to reach an impossible target which is the backend-agnostic acir, and for what benefit? |
I removed the usage of |
MacOS is taking nearly 5 hours to complete -- I'm going to redo the workflow |
Blocked by noir-lang/Planning#21. |
Good to merge? |
Related issue(s)
Resolves #
Description
Summary of changes
This PR generates RAM and ROM opcodes if they are supported by the backend.
This will allow aztec backend to use UP loopk-ups for memory operations
Test additions / changes
We need a backend which support the opcodes.
Checklist
cargo fmt
with default settings.Documentation needs