rust/src/test/ui/consts/const-eval/const_raw_ptr_ops2.stderr

error[E0080]: evaluation of constant value failed
  --> $DIR/const_raw_ptr_ops2.rs:9:26
   |
LL | const Z2: i32 = unsafe { *(42 as *const i32) };
   |                          ^^^^^^^^^^^^^^^^^^^ 0x2a is not a valid pointer

error[E0080]: evaluation of constant value failed
  --> $DIR/const_raw_ptr_ops2.rs:11:26
   |
LL | const Z3: i32 = unsafe { *(44 as *const i32) };
   |                          ^^^^^^^^^^^^^^^^^^^ 0x2c is not a valid pointer

error: aborting due to 2 previous errors

For more information about this error, try `rustc --explain E0080`.
adjust tests 2021-07-12 17:21:35 -05:00			`error[E0080]: evaluation of constant value failed`
remove const_raw_ptr_to_usize_cast feature 2021-07-10 04:33:42 -05: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 12:25:14 -05:00			`\|`
			`LL \| const Z2: i32 = unsafe { (42 as const i32) };`
adjust tests 2021-07-12 17:21:35 -05:00			`\| ^^^^^^^^^^^^^^^^^^^ 0x2a is not a valid pointer`
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 12:25:14 -05:00
adjust tests 2021-07-12 17:21:35 -05:00			`error[E0080]: evaluation of constant value failed`
remove const_raw_ptr_to_usize_cast feature 2021-07-10 04:33:42 -05:00			`--> $DIR/const_raw_ptr_ops2.rs:11: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 12:25:14 -05:00			`\|`
			`LL \| const Z3: i32 = unsafe { (44 as const i32) };`
adjust tests 2021-07-12 17:21:35 -05:00			`\| ^^^^^^^^^^^^^^^^^^^ 0x2c is not a valid pointer`
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 12:25:14 -05:00
remove const_raw_ptr_to_usize_cast feature 2021-07-10 04:33:42 -05: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 12:25:14 -05:00
adjust tests 2021-07-12 17:21:35 -05:00			For more information about this error, try `rustc --explain E0080`.