Skip to content
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

Generate getelementptr instead of inttoptr for ptr::invalid #121242

Closed
wants to merge 1 commit into from
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 16 additions & 10 deletions library/core/src/ptr/mod.rs
Original file line number Diff line number Diff line change
Expand Up @@ -590,11 +590,14 @@ pub const fn null_mut<T: ?Sized + Thin>() -> *mut T {
#[unstable(feature = "strict_provenance", issue = "95228")]
pub const fn without_provenance<T>(addr: usize) -> *const T {
// FIXME(strict_provenance_magic): I am magic and should be a compiler intrinsic.
// We use transmute rather than a cast so tools like Miri can tell that this
// is *not* the same as from_exposed_addr.
// SAFETY: every valid integer is also a valid pointer (as long as you don't dereference that
// pointer).
unsafe { mem::transmute(addr) }
// FIXME(maybe): simply transmute the address once codegen lowers that correctly.
// We offset the null pointer instead of using a cast so that this lowers to
// getelementptr instead of inttoptr.
// We use transmute instead of casting so that in miri the pointer truly
// has no provenance.
// SAFETY: on all current platforms, usize and pointers have the same layout,
// and the validity invariant of pointers is the same as that of integers
unsafe { mem::transmute::<_, *const T>(0usize).wrapping_byte_add(addr) }
}

/// Creates a new pointer that is dangling, but well-aligned.
Expand Down Expand Up @@ -632,11 +635,14 @@ pub const fn dangling<T>() -> *const T {
#[unstable(feature = "strict_provenance", issue = "95228")]
pub const fn without_provenance_mut<T>(addr: usize) -> *mut T {
// FIXME(strict_provenance_magic): I am magic and should be a compiler intrinsic.
// We use transmute rather than a cast so tools like Miri can tell that this
// is *not* the same as from_exposed_addr.
// SAFETY: every valid integer is also a valid pointer (as long as you don't dereference that
// pointer).
unsafe { mem::transmute(addr) }
// FIXME(maybe): simply transmute the address once codegen lowers that correctly.
// We offset the null pointer instead of using a cast so that this lowers to
// getelementptr instead of inttoptr.
// We use transmute instead of casting so that in miri the pointer truly
// has no provenance.
// SAFETY: on all current platforms, usize and pointers have the same layout,
// and the validity invariant of pointers is the same as that of integers
unsafe { mem::transmute::<_, *mut T>(0usize).wrapping_byte_add(addr) }
}

/// Creates a new pointer that is dangling, but well-aligned.
Expand Down
16 changes: 16 additions & 0 deletions tests/codegen/strict-provenance.rs
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
//@ compile-flags: -O

#![crate_type = "lib"]
#![feature(strict_provenance)]

use std::ptr;

// CHECK-LABEL: ptr @without_provenance(
// CHECK-SAME: [[USIZE:i[0-9]+]] noundef %addr)
#[no_mangle]
fn without_provenance(addr: usize) -> *const () {
// CHECK: start
// CHECK-NEXT: %0 = getelementptr i8, ptr null, [[USIZE]] %addr
// CHECK-NEXT: ret ptr %0
ptr::without_provenance(addr)
}
Loading