rust/tests/ui/consts/const-eval/const_raw_ptr_ops2.stderr

error[E0080]: evaluation of constant value failed
  --> $DIR/const_raw_ptr_ops2.rs:7:26
   |
LL | const Z2: i32 = unsafe { *(42 as *const i32) };
   |                          ^^^^^^^^^^^^^^^^^^^ memory access failed: expected a pointer to 4 bytes of memory, but got 0x2a[noalloc] which is a dangling pointer (it has no provenance)

error[E0080]: evaluation of constant value failed
  --> $DIR/const_raw_ptr_ops2.rs:9:26
   |
LL | const Z3: i32 = unsafe { *(44 as *const i32) };
   |                          ^^^^^^^^^^^^^^^^^^^ memory access failed: expected a pointer to 4 bytes of memory, but got 0x2c[noalloc] which is a dangling pointer (it has no provenance)

error: aborting due to 2 previous errors

For more information about this error, try `rustc --explain E0080`.
adjust tests 2021-07-13 00:21:35 +02:00			`error[E0080]: evaluation of constant value failed`
Stabilize `const_raw_ptr_deref` for `const T` This stabilizes dereferencing immutable raw pointers in const contexts. It does not stabilize `mut T` dereferencing. This is placed behind the `const_raw_mut_ptr_deref` feature gate. 2021-10-05 04:55:57 -04:00			`--> $DIR/const_raw_ptr_ops2.rs:7:26`
Remove the const_raw_ptr_comparison feature gate. We can never supply a meaningful implementation of this. Instead, the follow up commits will create two intrinsics that approximate comparisons: * `ptr_maybe_eq` * `ptr_maybe_ne` The fact that `ptr_maybe_eq(a, b)` is not necessarily the same value as `!ptr_maybe_ne(a, b)` is a symptom of this entire problem. 2020-06-12 19:25:14 +02:00			`\|`
			`LL \| const Z2: i32 = unsafe { (42 as const i32) };`
improve dangling/oob errors and make them more uniform 2024-07-27 18:09:50 +02:00			`\| ^^^^^^^^^^^^^^^^^^^ memory access failed: expected a pointer to 4 bytes of memory, but got 0x2a[noalloc] which is a dangling pointer (it has no provenance)`
Remove the const_raw_ptr_comparison feature gate. We can never supply a meaningful implementation of this. Instead, the follow up commits will create two intrinsics that approximate comparisons: * `ptr_maybe_eq` * `ptr_maybe_ne` The fact that `ptr_maybe_eq(a, b)` is not necessarily the same value as `!ptr_maybe_ne(a, b)` is a symptom of this entire problem. 2020-06-12 19:25:14 +02:00
adjust tests 2021-07-13 00:21:35 +02:00			`error[E0080]: evaluation of constant value failed`
Stabilize `const_raw_ptr_deref` for `const T` This stabilizes dereferencing immutable raw pointers in const contexts. It does not stabilize `mut T` dereferencing. This is placed behind the `const_raw_mut_ptr_deref` feature gate. 2021-10-05 04:55:57 -04:00			`--> $DIR/const_raw_ptr_ops2.rs:9:26`
Remove the const_raw_ptr_comparison feature gate. We can never supply a meaningful implementation of this. Instead, the follow up commits will create two intrinsics that approximate comparisons: * `ptr_maybe_eq` * `ptr_maybe_ne` The fact that `ptr_maybe_eq(a, b)` is not necessarily the same value as `!ptr_maybe_ne(a, b)` is a symptom of this entire problem. 2020-06-12 19:25:14 +02:00			`\|`
			`LL \| const Z3: i32 = unsafe { (44 as const i32) };`
improve dangling/oob errors and make them more uniform 2024-07-27 18:09:50 +02:00			`\| ^^^^^^^^^^^^^^^^^^^ memory access failed: expected a pointer to 4 bytes of memory, but got 0x2c[noalloc] which is a dangling pointer (it has no provenance)`
Remove the const_raw_ptr_comparison feature gate. We can never supply a meaningful implementation of this. Instead, the follow up commits will create two intrinsics that approximate comparisons: * `ptr_maybe_eq` * `ptr_maybe_ne` The fact that `ptr_maybe_eq(a, b)` is not necessarily the same value as `!ptr_maybe_ne(a, b)` is a symptom of this entire problem. 2020-06-12 19:25:14 +02:00
remove const_raw_ptr_to_usize_cast feature 2021-07-10 11:33:42 +02:00			`error: aborting due to 2 previous errors`
Remove the const_raw_ptr_comparison feature gate. We can never supply a meaningful implementation of this. Instead, the follow up commits will create two intrinsics that approximate comparisons: * `ptr_maybe_eq` * `ptr_maybe_ne` The fact that `ptr_maybe_eq(a, b)` is not necessarily the same value as `!ptr_maybe_ne(a, b)` is a symptom of this entire problem. 2020-06-12 19:25:14 +02:00
adjust tests 2021-07-13 00:21:35 +02:00			For more information about this error, try `rustc --explain E0080`.