Skip to content

Conversation

@resistor
Copy link
Collaborator

Resolves #9

@davidchisnall
Copy link

This will probably require some build-system changes.

@resistor
Copy link
Collaborator Author

This will probably require some build-system changes.

I hope not. The cheriot CPU already implies the XCheriot1 feature.

@davidchisnall
Copy link

At some point, we want to get rid of the cheriot CPU name and have cheriot-sail, cheriot-ibex, and so on.

@resistor
Copy link
Collaborator Author

At some point, we want to get rid of the cheriot CPU name and have cheriot-sail, cheriot-ibex, and so on.

We'll definitely need build system changes for that!

@resistor resistor force-pushed the attr branch 2 times, most recently from e3ad194 to 5593ea4 Compare May 14, 2025 14:01
@resistor resistor changed the title [CHERIoT] Clean up direct references to the "cheriot" CPU name in favor of FeatureVendorXCheriot1 [CHERIoT] Clean up direct references to the "cheriot" CPU name in favor of FeatureVendorXCheriot1V May 14, 2025
@resistor
Copy link
Collaborator Author

Manually tested the RTOS test suite build with this change.

@resistor resistor changed the title [CHERIoT] Clean up direct references to the "cheriot" CPU name in favor of FeatureVendorXCheriot1V [CHERIoT] Clean up direct references to the "cheriot" CPU name in favor of FeatureVendorXCheriot May 14, 2025
@resistor resistor merged commit 1153d07 into CHERIoT-Platform:cheriot May 15, 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.

cheriot is not a CPU name

2 participants