rust/tests/ui/consts/issue-83182.stderr

error[E0080]: it is undefined behavior to use this value
  --> $DIR/issue-83182.rs:7:1
   |
LL | const MYSTR_NO_INIT: &MyStr = unsafe { mem::transmute::<&[_], _>(&[&()]) };
   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ unable to turn pointer into raw bytes
   |
   = note: the raw bytes of the constant (size: $SIZE, align: $ALIGN) {
               HEX_DUMP
           }
   = 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`.
handle pointers in str 2021-05-15 08:04:41 -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/issue-83182.rs:7:1`
handle pointers in str 2021-05-15 08:04:41 -05:00			`\|`
			`LL \| const MYSTR_NO_INIT: &MyStr = unsafe { mem::transmute::<&[_], _>(&[&()]) };`
adjust tests 2022-08-27 16:46:14 -05:00			`\| ^^^^^^^^^^^^^^^^^^^^^^^^^^^ unable to turn pointer into raw bytes`
handle pointers in str 2021-05-15 08:04:41 -05:00			`\|`
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`
handle pointers in str 2021-05-15 08:04:41 -05: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`
handle pointers in str 2021-05-15 08:04:41 -05:00
			`error: aborting due to previous error`

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