-
Notifications
You must be signed in to change notification settings - Fork 13.3k
make std::intrinsics functions actually be intrinsics #139916
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
base: master
Are you sure you want to change the base?
Conversation
rustbot has assigned @Mark-Simulacrum. Use |
This comment has been minimized.
This comment has been minimized.
0497c07
to
82d5e7a
Compare
This comment has been minimized.
This comment has been minimized.
82d5e7a
to
5a7d62b
Compare
This comment has been minimized.
This comment has been minimized.
5a7d62b
to
5d60226
Compare
I'd be interested in seeing a crater run on that, to be honest. We've pulled the rug on things that were accidentally stabilized before, even long after the fact. |
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.
r=me with test confirmed to be adjusted as expected
@@ -45,7 +45,7 @@ | |||
_9 = copy _10; | |||
_8 = move _9 as *mut i32 (PtrToPtr); | |||
StorageDead(_9); | |||
- _3 = copy_nonoverlapping::<i32>(move _4, move _8, const 0_usize) -> [return: bb1, unwind unreachable]; | |||
- _3 = std::intrinsics::copy_nonoverlapping::<i32>(move _4, move _8, const 0_usize) -> [return: bb1, unwind unreachable]; | |||
+ copy_nonoverlapping(dst = move _8, src = move _4, count = const 0_usize); |
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'm confused why this changed - maybe I'm missing something but the test looks like it's supposed to already call the intrinsic? Is this change ok?
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.
Note that only the "old" line changed -- it is now using std::intrinsics::copy_nonoverlapping
rather than the local copy_nonoverlapping
, which is expected as that is exactly what changed in the rs file.
The "new" line, in both cases, is the MIR statement form of copy_nonoverlapping
.
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.
Oh, right, this is a diff of a diff. Okay, makes sense.
Since this is a slight breaking change (of accidentally-stable API surface), does it need an FCP of some sort -- from @rust-lang/libs-api, I assume? |
FCP since this is very slightly breaking, though unlikely to cause any issues in practice. @rfcbot merge |
Team member @Amanieu has proposed to merge this. The next step is review by the rest of the tagged team members: No concerns currently listed. Once a majority of reviewers approve (and at most 2 approvals are outstanding), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up! See this document for info about what commands tagged team members can give me. |
@bors try |
make std::intrinsic functions actually be intrinsics Most of the functions in `std::intrinsics` are actually intrinsics, but some are not: for historical reasons, `std::intrinsics::{copy,copy_nonoverlapping,write_bytes}` are accessible on stable, and the versions in `std::ptr` are just re-exports. These functions are not intrinsics, but wrappers around the intrinsic, because they add extra debug assertions. This PR makes the functions in `std::intrinsics` actually be intrinsics. - The advantage is that we can now use it in tests that need to directly call the intrinsic, thus removing a footgun for compiler development. We also remove the extended user-facing doc comments of these functions out of a file that should be largely internal documentation. - The downside is that if users are using those functions directly, they will not get the debug assertions any more. Note however that those users are already ignoring a deprecation warning, so I think this is fine. Furthermore, if someone imports the `intrinsic` name of this function and turns that into a function pointer, that will no longer work, since only the wrapper functions can be turned into a function pointer. I would be rather surprised if anyone did this, though... and again, they must have already ignored a deprecation warning. Still, seems worth a crater run, if there's general agreement that we want to go ahead with this change. (`intrinsics::drop_in_place` also remains not-an-intrinsic, which bugs me, but oh well, not much we can do about it; we can't remove it from the module as the path is accidentally-stable.) Cc `@rust-lang/libs-api` `@saethlin`
☀️ Try build successful - checks-actions |
@craterbot check |
👌 Experiment ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more |
🚧 Experiment ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more |
🎉 Experiment
|
These all look spurious :) |
Big fan of letting tests just use the versions from |
Most of the functions in
std::intrinsics
are actually intrinsics, but some are not: for historical reasons,std::intrinsics::{copy,copy_nonoverlapping,write_bytes}
are accessible on stable, and the versions instd::ptr
are just re-exports. These functions are not intrinsics, but wrappers around the intrinsic, because they add extra debug assertions.This PR makes the functions in
std::intrinsics
actually be intrinsics.intrinsic
name of this function and turns that into a function pointer, that will no longer work, since only the wrapper functions can be turned into a function pointer. I would be rather surprised if anyone did this, though... and again, they must have already ignored a deprecation warning. Still, seems worth a crater run, if there's general agreement that we want to go ahead with this change.(
intrinsics::drop_in_place
also remains not-an-intrinsic, which bugs me, but oh well, not much we can do about it; we can't remove it from the module as the path is accidentally-stable.)Cc @rust-lang/libs-api @saethlin