Today in "RISC-V is incredibly vague about important things": they changed the wording in the spec to imply that writing to one half of `mcycle` or `minstret` suppresses the increment of the other half.

I thought the old wording was pretty clear and I actually had a test that it did *not* do that.

Is it good when the source code for your processor has to reference github issues to clarify spec details?

Git patch that is basically me being passive aggressive about what a shitshow the RISC-V spec is (very passive though)

On a more positive note I have been liking `surfer` quite a bit. It's pretty much a less-crusty GTKWave.

My favourite feature: clicking on a signal and pressing the DELETE key deletes the signal.

0

If you have a fediverse account, you can quote this note from your own instance. Search https://types.pl/users/wren6991/statuses/115561603037172008 on your instance and quote it. (Note that quoting is not supported in Mastodon.)