Skip to content

Conversation

@resistor
Copy link
Collaborator

No description provided.

@resistor resistor force-pushed the xcheriot branch 2 times, most recently from 9836c44 to ed731d9 Compare May 13, 2025 11:34
@davidchisnall
Copy link

Someone pointed out that the normal versioning scheme for RISC-V doesn't include a v, so the canonical name for this would be Xcheriot1, where Xcheriot would default to whatever the latest supported version is.

svpbmt 1.0
svvptc 1.0
xcheri 0.0
xcheriotv1 0.0

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't this be xcheriot 1.0?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

@resistor
Copy link
Collaborator Author

Someone pointed out that the normal versioning scheme for RISC-V doesn't include a v, so the canonical name for this would be Xcheriot1, where Xcheriot would default to whatever the latest supported version is.

Since this isn't end-user facing, I don't think it makes sense to have "Xcheriot" alias to latest version. At this level, I think we'd prefer explicitness and easy reproducibility.

@resistor resistor force-pushed the xcheriot branch 2 times, most recently from 67ad24c to 5fba0bf Compare May 13, 2025 11:56
@resistor resistor changed the title [CHERIoT] Create an XCheriotV1 processor feature. [CHERIoT] Create an XCheriot1 processor feature. May 13, 2025
@resistor
Copy link
Collaborator Author

Changed the feature name to XCheriot1 and bumped the version number to 1.0.

@resistor resistor merged commit e91f708 into CHERIoT-Platform:cheriot May 14, 2025
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants