Add CHERI-specific built-ins and use them in core::ptr
#23
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
xdoardo
changed the title
core::ptr. core::ptr
seharris
reviewed
Sep 12, 2025
|
This is a really small nitpick because it's just aesthetic, but I feel like it would be slightly tidier to match the existing code and use |
xdoardo
force-pushed
the
cheri-built-ins
branch
from
dcc6570 to
c322356
Compare
Fixed with c322356, which also removes the |
…ovenance` intrinsics
xdoardo
force-pushed
the
cheri-built-ins
branch
from
c322356 to
a4cc0f1
Compare
seharris
approved these changes
Sep 17, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since simply casting an
usizeto a raw pointer will incur a compilation error, I think we need built-ins to create pointers without provenance and to get the address part of a pointer with provenance.