-
Notifications
You must be signed in to change notification settings - Fork 706
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
Add the Zc* ISA to "Applicable Specifications" #1615
Add the Zc* ISA to "Applicable Specifications" #1615
Conversation
✔️ successful run, report available here. |
@Gchauvon The I$ and D$ are present in CV32A60B, can you add a commit to indicate the configuration you have currently implemented. |
|
||
+--------------------+---------+---------+------+-------+---------+---------+---------+---------+ | ||
| Release ID | Target | ISA | XLEN | FPU | CV-X-IF | MMU | L1 D$ | L1 I$ | | ||
+====================+=========+=========+======+=======+=========+=========+=========+=========+ | ||
| CV32A60B | ASIC | IMC | 32 | No | Yes | None | None | None | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Following a Cores TG meeting:
CV32A60B is not accepted as the "embedded" configuration is not an application core.
The following part numbers are proposed:
- CV32E60X if we keep the single issue
- CV32E6?X (e.g. CV32E62X, CV32E65X...) if the configuration includes the dual issue, to reflect the higher performance. (My side note: don't use CV32E64X that would surely bring confusion).
I suggest to replace CV32A60X by CV32E6?X for this document and we'll update when the single-issue/dual-issue configuration is decived.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to call it "Embedded", "CV32A60B", "CV32E62X", "CV32E65X", "CV32E60X" or "CV32E6?X" What a mess !!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have updated the PR with a proposal.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Superseded by a new commit.
✔️ successful run, report available here. |
@MikeOpenHWGroup With you respect, I have updated directly into your branch some cache information. @jquevremont can you merge ? |
✔️ successful run, report available here. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
During the CVA6 Verification meeting today (2023-11-09) it was pointed out that we have not defined the version of the Zc* ISA extension we support. This is a recently ratified spec. and it is not easy to find, so this PR (attempts to) resolve that.
Since I was already editing the
cva6_requirements_specification.rst
doc, I took the liberty of adding the CV32A60B, although I am not sure if the configuration information I added is correct.