Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Define 'G' ISA name as including Zifencei and Zicsr #266

Closed
asb opened this issue Nov 12, 2018 · 3 comments
Closed

Define 'G' ISA name as including Zifencei and Zicsr #266

asb opened this issue Nov 12, 2018 · 3 comments

Comments

@asb
Copy link
Contributor

asb commented Nov 12, 2018

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.

@aswaterman
Copy link
Member

Agreed.

@dkruckemyer-ventana
Copy link
Contributor

dkruckemyer-ventana commented Feb 27, 2019

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....)

@dkruckemyer-ventana
Copy link
Contributor

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).

Never mind....

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants