Provide stable equivalent of #![feature(strict_provenance_atomic_ptr)] #23
Conversation
This file contains 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
- `AtomicPtr::fetch_ptr_{add,sub}`
- `AtomicPtr::fetch_byte_{add,sub}`
- `AtomicPtr::fetch_{or,and,xor}`
These APIs are compatible with strict-provenance on `cfg(miri)`.
Otherwise, they are compatible with permissive-provenance.
Once `#![feature(strict_provenance_atomic_ptr)]` is stabilized,
these APIs will be strict-provenance compatible in all cases from the
version in which it is stabilized.
|
bors r+ |
|
Build succeeded: |
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.
This provides stable equivalent of
#![feature(strict_provenance_atomic_ptr)].AtomicPtr::fetch_ptr_{add,sub}AtomicPtr::fetch_byte_{add,sub}AtomicPtr::fetch_{or,and,xor}These APIs are compatible with strict-provenance on
cfg(miri).Otherwise, they are compatible with permissive-provenance.
Once
#![feature(strict_provenance_atomic_ptr)]is stabilized, these APIs will be strict-provenance compatible in all cases from the version in which it is stabilized.(This is also a generalization of what I did in crossbeam-epoch.)