Claire Wolf

> (defaults to 32 bits) [..] The 12345 is assumed to be 32 bits wide. This is not correct. The Verilog standard says that unsized constants must be _at least_...

> Yosys may do the smart thing, but the standard is obviously ambiguous. Yes, the standard is ambiguous, but only for constants that do not fit in 32 bits! There...

To further elaborate, I thing the following two conditions should trigger a warning in a Verilog linter: 1. Use of unsized constants in certain self-sized contexts, such as `{...}` or...

Merged it into my `gcc.diff`, and made some quick changes in 7d57261 to make the flags additive. Talking about `gcc.diff`: Clearly that's a horrible solution going forward! I think it...

Hmm.. I could swear https://github.com/riscv/riscv-gcc didn't exist when I created `gcc.diff`. Is it a relatively new repo? I don't have write access to that repo though. I think `riscv-isa-sim` is...

I reverted 7d57261 and 7266bf2. We'll move the gcc patch to a gcc github branch soon. Let's merge your new patch when this is done. Leaving this issue open until...

Bruce Hoult just mentioned this issue to me in a private email and I have an alternative suggestion for the instruction length encoding: ``` x FFF RRRRR ??bbb11 32-bit (bbb...

> One point is there is no explicit mention of what to do with FP literals which I think are at least as important as integer ones. One option is...

Another obvious use for a "major opcode" would be mirrors of the 32-bit OP and OP-FP opcode spaces, with large immediates. Theres a neat encoding for this that I really...

I've expanded a bit on the above ideas and posted the resulting proposal here: http://svn.clifford.at/handicraft/2019/rvlonginsn/README