…ztecProtocol/aztec-packages#5208)

Fixes #4544 and
#4543

…#5217)

The AVM cannot support setting constants of field size (because the whole instruction has to fit in a field). To align Brillig with AVM bytecode, I'm changing bytecode emission for the case where the constant is > 128 bits.

The current change splits the field into two 128bit limbs, and then multiplies and adds.

…#5217)

The AVM cannot support setting constants of field size (because the whole instruction has to fit in a field). To align Brillig with AVM bytecode, I'm changing bytecode emission for the case where the constant is > 128 bits.

The current change splits the field into two 128bit limbs, and then multiplies and adds.

Split brillig IR in low level instructions and higher level codegen
files that compose the instructions and restrict visibilities. This
should not have any business logic change. This also fixes debug_show by
only printing the low level instructions, previously we were printing
both the high level codegen and the low level instructions and it was a
mess to read.

Split brillig IR in low level instructions and higher level codegen
files that compose the instructions and restrict visibilities. This
should not have any business logic change. This also fixes debug_show by
only printing the low level instructions, previously we were printing
both the high level codegen and the low level instructions and it was a
mess to read.

---------

Co-authored-by: Álvaro Rodríguez <sirasistant@gmail.com>

---------

Co-authored-by: Álvaro Rodríguez <sirasistant@gmail.com>

…mage (AztecProtocol/aztec-packages#5222)

Checks that the msg.sender in initializer calls matches the deployer
address defined in the address preimage, unless when it's set to zero.

…mage (AztecProtocol/aztec-packages#5222)

Checks that the msg.sender in initializer calls matches the deployer
address defined in the address preimage, unless when it's set to zero.