Santiago Arranz Olmos

I think it could be a good idea, as the error might come from the user not actually pointing to a file that's not there but using an option incorrectly.

Note that for the first part, we could reuse `arm_cmd_load_large_imm` from `arm_params`, that is already proven to have the appropriate semantics. But it's done for `fexpr`s, se we could maybe...

No, because it triggers #478.

I'm not sure who's supposed to report the error here, for this case I would be ok with changing the error at assembly generation. But it's true that in general...

Two more examples, perhaps less artificial: ``` export fn main() -> reg u64 { reg u64 x; x = 0; x = 1 - x; return x; } ``` and...