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
I think it's expected that any "general-purpose" core provides these extensions, so it would seem consistent to maintain their presence in the RV32G/RV64G ISAs.
The text was updated successfully, but these errors were encountered:
There seems to be uncertainty in the memory model group (and possibly the J-extension group) discussions about the definition and implications of the FENCE.I instruction for certain classes of systems (e.g. large scale servers). Since these systems will most likely run Unix and the Unix platform working group will likely require RV64GC[...], this definition implies that all cores implemented for Unix will be required to implement FENCE.I as defined by Zifencei (as well as whatever else is defined to perform instruction cache maintenance).
Though this ship may have sailed, that requirement doesn't seem desirable.... (FWIW, the Zicsr requirement seems OK to me....)
OK. My bad. I just reread the definition and commentary for Zifencei, and the definition of FENCE.I seems to be relaxed from what I remember from before (in particular, I thought there was a multiprocessor requirement, but that's not the case).
I think it's expected that any "general-purpose" core provides these extensions, so it would seem consistent to maintain their presence in the RV32G/RV64G ISAs.
The text was updated successfully, but these errors were encountered: