-
Notifications
You must be signed in to change notification settings - Fork 272
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
chore: Use BrilligCall for unconstrained main and update AVM transpiler #5795
Conversation
} | ||
|
||
/// Print inputs, outputs, and instructions in a Brillig program | ||
pub fn dbg_print_brillig_program(brillig: &Brillig) { | ||
pub fn dbg_print_brillig_program(brillig_bytecode: &[BrilligOpcode]) { |
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.
I figuredi t would be fine to just print the bytecode as the AVM transpiler doesn't look to touch the inputs/outputs at all, we only print instructions for the AVM program, and you can get the Brillig inputs/outputs by printing the ACIR.
This could probably do with a rebase on top of master. |
Co-authored-by: Tom French <[email protected]>
Co-authored-by: jfecher <[email protected]>
Co-authored-by: jfecher <[email protected]>
…ir/acir_variable.rs Co-authored-by: jfecher <[email protected]>
…ir/acir_variable.rs Co-authored-by: jfecher <[email protected]>
…ir/acir_variable.rs Co-authored-by: jfecher <[email protected]>
…ir/acir_variable.rs Co-authored-by: jfecher <[email protected]>
…ir/acir_variable.rs Co-authored-by: jfecher <[email protected]>
…ir/acir_variable.rs Co-authored-by: jfecher <[email protected]>
Co-authored-by: jfecher <[email protected]>
6601d1a
to
14b9ae8
Compare
This commit history is really ugly and I messed up the rebase so this PR has been superseded by 5797 |
A follow-up to #5737
Separate PR as this touches mainly the AVM transpiler and not Noir codegen itself. Look in PR #5737 for full details about the switch, but basically we are moving away from the
Brillig
opcode to aBrilligCall
opcode that contains a Brillig call opcode. The AVM needs to be updated to account for this change.