Alessandro Gatti

@dpgeorge fyi, MICROBIT crashes when accessing the function table, which doesn't make much sense. *Edit*: unless the ROM cannot be read from RAM or some other protection mechanism like that?...

This should now work with the changes to the test runner made after 1.24.0. This PR also makes the test runner able to detect if inline assembler support is enabled...

I'm wondering on what's the policy for new test files after the introduction of `unittest`. Should the test files contained in this PR be moved to that framework (as in,...

> > * Compressed opcodes start with the `c.` prefix [...] > Do you think it's worth trying to match the syntax more closely here, and use `c.` as the...

`RULE_atom_expr_normal` unfortunately fails on expressions like `lw(a0, -4(sp))`, in that case it matches `RULE_factor_2`. I'll work around that somehow.

This is still missing the syntax error tests - I just pushed the code so the C code changes can be reviewed as I'm not 100% sure whether the new...

> When an rv32 inline-asm function is entered into, what registers are automatically saved? Is there anything else done in the prelude? The prelude saves the function table pointer and...

OK, this should be it I guess. I wish the offset-to-register syntax support wasn't bolted on this way, but it works :) That can be cleaned up for v2 anyway.

Indeed, everything else fits in nicely without special cases and exceptions. It's more of a personal preference, really, but re-designing everything to cover that case in a generic way as...

Done. Maybe when more targets will support `cm.push`/`cm.popret` opcodes (right now only the pico2 does) it can be feasible to automatically save/restore RA + S0..S11 with an explicit opt-out via...