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
Currently the way we build the RISCV machine powdr-asm code is quite ugly imo, with a bunch of String concatenations that look quite messy. Ideally we should have a template file in powdr-asm that simply gets filled by the Rust code that collects the info needed about registers, instructions, continuations etc and renders the final machine.
Example:
use std::machines::memory::{{memory_machine}};{{ binary_import }}{{ shift_import }}{{ split_import }}{{ poseidon_import }}{{ arith_import }}// could actually always import all, don't think it hurts compilation
machine Main{
reg val1;
reg val2;{{ extra_registers }}
col witness va1_col;
col witness va2_col;
col witness va3_col;
col witness va3_col;// ... all base instructions{{ binary_instructions }}{{ shift_instructions }}{{ poseidon_instructions }}{{ arith_instructions }}function main {{{ code }}}}
The text was updated successfully, but these errors were encountered:
Currently the way we build the RISCV machine powdr-asm code is quite ugly imo, with a bunch of String concatenations that look quite messy. Ideally we should have a template file in powdr-asm that simply gets filled by the Rust code that collects the info needed about registers, instructions, continuations etc and renders the final machine.
Example:
The text was updated successfully, but these errors were encountered: