rust/tests/ui/consts/miri_unleashed/ptr_arith.stderr

error[E0080]: could not evaluate static initializer
  --> $DIR/ptr_arith.rs:8:13
   |
LL |     let x = &0 as *const _ as usize;
   |             ^^^^^^^^^^^^^^^^^^^^^^^ exposing pointers is not possible at compile-time

error[E0080]: could not evaluate static initializer
  --> $DIR/ptr_arith.rs:16:14
   |
LL |     let _v = x + 0;
   |              ^ unable to turn pointer into integer
   |
   = help: this code performed an operation that depends on the underlying bytes representing a pointer
   = help: the absolute address of a pointer is not known at compile-time, so such operations are not supported

warning: skipping const checks
   |
help: skipping check that does not even have a feature gate
  --> $DIR/ptr_arith.rs:8:13
   |
LL |     let x = &0 as *const _ as usize;
   |             ^^^^^^^^^^^^^^^^^^^^^^^

error: aborting due to 2 previous errors; 1 warning emitted

For more information about this error, try `rustc --explain E0080`.
make sure even unleashed miri does not do pointer stuff 2020-05-14 16:29:50 -05:00			`error[E0080]: could not evaluate static initializer`
make const_err a hard error 2022-09-21 06:05:20 -05:00			`--> $DIR/ptr_arith.rs:8:13`
test dynamic check for ptr-int-casts (unleashed) 2021-07-12 17:25:31 -05:00			`\|`
			`LL \| let x = &0 as *const _ as usize;`
CTFE: exposing pointers and calling extern fn doesn't need an RFC, it is just impossible 2022-08-28 12:13:13 -05:00			`\| ^^^^^^^^^^^^^^^^^^^^^^^ exposing pointers is not possible at compile-time`
test dynamic check for ptr-int-casts (unleashed) 2021-07-12 17:25:31 -05:00
			`error[E0080]: could not evaluate static initializer`
make const_err a hard error 2022-09-21 06:05:20 -05:00			`--> $DIR/ptr_arith.rs:16:14`
make sure even unleashed miri does not do pointer stuff 2020-05-14 16:29:50 -05:00			`\|`
			`LL \| let _v = x + 0;`
const validation: point at where we found a pointer but expected an integer 2023-08-02 09:14:36 -05:00			`\| ^ unable to turn pointer into integer`
adjust tests 2022-08-27 16:46:14 -05:00			`\|`
			`= help: this code performed an operation that depends on the underlying bytes representing a pointer`
			`= help: the absolute address of a pointer is not known at compile-time, so such operations are not supported`
make sure even unleashed miri does not do pointer stuff 2020-05-14 16:29:50 -05:00
			`warning: skipping const checks`
			`\|`
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			`help: skipping check that does not even have a feature gate`
make const_err a hard error 2022-09-21 06:05:20 -05:00			`--> $DIR/ptr_arith.rs:8:13`
test dynamic check for ptr-int-casts (unleashed) 2021-07-12 17:25:31 -05:00			`\|`
			`LL \| let x = &0 as *const _ as usize;`
			`\| ^^^^^^^^^^^^^^^^^^^^^^^`
make sure even unleashed miri does not do pointer stuff 2020-05-14 16:29:50 -05:00
bless tests, remove nonexistent E0395 2022-07-25 03:17:00 -05:00			`error: aborting due to 2 previous errors; 1 warning emitted`
make sure even unleashed miri does not do pointer stuff 2020-05-14 16:29:50 -05:00
			For more information about this error, try `rustc --explain E0080`.