rust/tests/ui/consts/const-eval/ub-uninhabit.stderr

error[E0080]: evaluation of constant value failed
  --> $DIR/ub-uninhabit.rs:16:35
   |
LL | const BAD_BAD_BAD: Bar = unsafe { MaybeUninit { uninit: () }.init };
   |                                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ constructing invalid value: encountered a value of uninhabited type `Bar`

error[E0080]: it is undefined behavior to use this value
  --> $DIR/ub-uninhabit.rs:19:1
   |
LL | const BAD_BAD_REF: &Bar = unsafe { mem::transmute(1usize) };
   | ^^^^^^^^^^^^^^^^^^^^^^^ constructing invalid value: encountered a reference pointing to uninhabited type Bar
   |
   = note: The rules on what exactly is undefined behavior aren't clear, so this check might be overzealous. Please open an issue on the rustc repository if you believe it should not be considered undefined behavior.
   = note: the raw bytes of the constant (size: $SIZE, align: $ALIGN) {
               HEX_DUMP
           }

error[E0080]: evaluation of constant value failed
  --> $DIR/ub-uninhabit.rs:22:42
   |
LL | const BAD_BAD_ARRAY: [Bar; 1] = unsafe { MaybeUninit { uninit: () }.init };
   |                                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ constructing invalid value at [0]: encountered a value of uninhabited type `Bar`

error: aborting due to 3 previous errors

For more information about this error, try `rustc --explain E0080`.
Detect uninhabited types early in const eval. 2023-03-21 05:20:00 -05:00			`error[E0080]: evaluation of constant value failed`
			`--> $DIR/ub-uninhabit.rs:16:35`
Add 32bit.stderr files. 2021-03-31 04:33:45 -05:00			`\|`
			`LL \| const BAD_BAD_BAD: Bar = unsafe { MaybeUninit { uninit: () }.init };`
Use translatable diagnostics in `rustc_const_eval` 2023-05-17 05:30:14 -05:00			\| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ constructing invalid value: encountered a value of uninhabited type `Bar`
Add 32bit.stderr files. 2021-03-31 04:33:45 -05:00
			`error[E0080]: it is undefined behavior to use this value`
Fix ui constant tests for big-endian platforms A number of tests under ui/const-ptr and ui/consts are currently failing on big-endian platforms as the binary encoding of some constants is hard-coded in the stderr test files. Fix this by providing a normalize-stderr-test rule that strips out the raw bytes hex dump, so the comparison can be done in an endianness-independent manner. Note that in most cases, this means the tests are now also independent of word size, so the 32bit and 64bit cases can be re-unified. To keep tests that verify the details of those raw bytes dumps, a new test case raw-bytes.rs performs the tests where the hex dumps were stripped out a second time, but only on little- endian platforms. In addition, src/test/ui/const-ptr/forbidden_slices.rs exposes an endian-specific difference in this diagnostic output: constructing invalid value at .<deref>[0]: encountered 0x11, but expected a boolean depending on which byte of D0 is not a boolean value (0 or 1). Fixed this by choosing a value of D0 that differs from 0 or 1 in all bytes. Fixes part of https://github.com/rust-lang/rust/issues/105383. 2022-12-22 09:40:50 -06:00			`--> $DIR/ub-uninhabit.rs:19:1`
Add 32bit.stderr files. 2021-03-31 04:33:45 -05:00			`\|`
			`LL \| const BAD_BAD_REF: &Bar = unsafe { mem::transmute(1usize) };`
Shorten def_span for more items. 2022-02-13 09:27:59 -06:00			`\| ^^^^^^^^^^^^^^^^^^^^^^^ constructing invalid value: encountered a reference pointing to uninhabited type Bar`
Add 32bit.stderr files. 2021-03-31 04:33:45 -05:00			`\|`
			`= note: The rules on what exactly is undefined behavior aren't clear, so this check might be overzealous. Please open an issue on the rustc repository if you believe it should not be considered undefined behavior.`
Fix ui constant tests for big-endian platforms A number of tests under ui/const-ptr and ui/consts are currently failing on big-endian platforms as the binary encoding of some constants is hard-coded in the stderr test files. Fix this by providing a normalize-stderr-test rule that strips out the raw bytes hex dump, so the comparison can be done in an endianness-independent manner. Note that in most cases, this means the tests are now also independent of word size, so the 32bit and 64bit cases can be re-unified. To keep tests that verify the details of those raw bytes dumps, a new test case raw-bytes.rs performs the tests where the hex dumps were stripped out a second time, but only on little- endian platforms. In addition, src/test/ui/const-ptr/forbidden_slices.rs exposes an endian-specific difference in this diagnostic output: constructing invalid value at .<deref>[0]: encountered 0x11, but expected a boolean depending on which byte of D0 is not a boolean value (0 or 1). Fixed this by choosing a value of D0 that differs from 0 or 1 in all bytes. Fixes part of https://github.com/rust-lang/rust/issues/105383. 2022-12-22 09:40:50 -06:00			`= note: the raw bytes of the constant (size: $SIZE, align: $ALIGN) {`
			`HEX_DUMP`
Add 32bit.stderr files. 2021-03-31 04:33:45 -05:00			`}`

Detect uninhabited types early in const eval. 2023-03-21 05:20:00 -05:00			`error[E0080]: evaluation of constant value failed`
			`--> $DIR/ub-uninhabit.rs:22:42`
Add 32bit.stderr files. 2021-03-31 04:33:45 -05:00			`\|`
			`LL \| const BAD_BAD_ARRAY: [Bar; 1] = unsafe { MaybeUninit { uninit: () }.init };`
Use translatable diagnostics in `rustc_const_eval` 2023-05-17 05:30:14 -05:00			\| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ constructing invalid value at [0]: encountered a value of uninhabited type `Bar`
Add 32bit.stderr files. 2021-03-31 04:33:45 -05:00
			`error: aborting due to 3 previous errors`

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