You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Most formal specs I've read define words like "should", "must", "may", up front, but the RISC-V spec does not appear to. Despite that "should" appears dozens of times, often in places where it looks like they really meant "must", e.g.
In systems without S-mode, the medeleg and mideleg registers should not exist.
An Exception Code of 0 is reserved to mean "unknown cause" and implementations that do not distinguish sources of NMIs via the mcause register should return 0 in the Exception Code.
I think it would be helpful to audit those and probably change them to must.
Most formal specs I've read define words like "should", "must", "may", up front, but the RISC-V spec does not appear to. Despite that "should" appears dozens of times, often in places where it looks like they really meant "must", e.g.
I think it would be helpful to audit those and probably change them to must.
Ideally adopt RFC2119 definitions and use them.
The text was updated successfully, but these errors were encountered: