rust/tests/ui/consts/issue-miri-1910.stderr

error[E0080]: evaluation of constant value failed
  --> $SRC_DIR/core/src/ptr/mod.rs:LL:COL
   |
   = note: unable to turn pointer into raw bytes
   |
note: inside `std::ptr::read::<u8>`
  --> $SRC_DIR/core/src/ptr/mod.rs:LL:COL
note: inside `ptr::const_ptr::<impl *const u8>::read`
  --> $SRC_DIR/core/src/ptr/const_ptr.rs:LL:COL
note: inside `C`
  --> $DIR/issue-miri-1910.rs:7:5
   |
LL |     (&foo as *const _ as *const u8).add(one_and_a_half_pointers).read();
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   = 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

error: aborting due to previous error

For more information about this error, try `rustc --explain E0080`.
make const_err a hard error 2022-09-21 06:05:20 -05:00			`error[E0080]: evaluation of constant value failed`
fix ICE on Miri/CTFE copy of half a pointer 2021-11-13 19:55:33 -06:00			`--> $SRC_DIR/core/src/ptr/mod.rs:LL:COL`
			`\|`
`MaybeUninit::assume_init_read` should have `noundef` load metadata I was looking into `array::IntoIter` optimization, and noticed that it wasn't annotating the loads with `noundef` for simple things like `array::IntoIter<i32, N>`. Turned out to be a more general problem as `MaybeUninit::assume_init_read` isn't marking the load as initialized (<https://rust.godbolt.org/z/Mxd8TPTnv>), which is unfortunate since that's basically its reason to exist. This PR lowers `ptr::read(p)` to `copy *p` in MIR, which fortuitiously also improves the IR we give to LLVM for things like `mem::replace`. 2023-03-11 17:32:54 -06:00			`= note: unable to turn pointer into raw bytes`
fix ICE on Miri/CTFE copy of half a pointer 2021-11-13 19:55:33 -06:00			`\|`
Change CTFE backtraces to use `note` instead of `label` to preserve their order labels are reordered within the file in which they are reported, which can mess up the stack trace 2022-11-29 07:10:42 -06:00			note: inside `std::ptr::read::<u8>`
			`--> $SRC_DIR/core/src/ptr/mod.rs:LL:COL`
			note: inside `ptr::const_ptr::<impl *const u8>::read`
			`--> $SRC_DIR/core/src/ptr/const_ptr.rs:LL:COL`
			note: inside `C`
Stabilize const_ptr_read 2023-05-05 07:50:59 -05:00			`--> $DIR/issue-miri-1910.rs:7:5`
make const_err show up in future breakage reports 2022-06-04 10:06:04 -05:00			`\|`
make const_err a hard error 2022-09-21 06:05:20 -05:00			`LL \| (&foo as const _ as const u8).add(one_and_a_half_pointers).read();`
Change CTFE backtraces to use `note` instead of `label` to preserve their order labels are reordered within the file in which they are reported, which can mess up the stack trace 2022-11-29 07:10:42 -06:00			`\| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^`
Use translatable diagnostics in `rustc_const_eval` 2023-05-17 05:30: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 const_err show up in future breakage reports 2022-06-04 10:06:04 -05:00
make const_err a hard error 2022-09-21 06:05:20 -05:00			`error: aborting due to previous error`

			For more information about this error, try `rustc --explain E0080`.