I used to have a formally verified correct RISC-V core. With the release of v2.3 it will be out of spec. What happened to no backwards incompatible changes after v2.0? What happened to spike is the executable golden reference? It's all lies..
-
-
Show this thread
-
Rocket of course used to be out of spec up to and including v2.2 of the spec. Starting with v2.3 rocket will magically be in spec and every other implementation that did it correct before will suddenly be in violation of the spec. Nothing matters.
Show this thread -
For what it's worth:https://groups.google.com/a/groups.riscv.org/forum/#!topic/isa-dev/oT1r-owKicY …
Show this thread
End of conversation
New conversation -
-
-
Why is that important?
-
Because it means that valid code that compilers might generate for v2.3 and latter of the spec will trigger an illegal instruction trap on the processors that implemented the old version of the spec correctly.
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.