diff options
| author | Ulrich Weigand <ulrich.weigand@de.ibm.com> | 2023-08-24 12:44:42 +0200 |
|---|---|---|
| committer | Ulrich Weigand <ulrich.weigand@de.ibm.com> | 2023-08-24 12:49:53 +0200 |
| commit | 2063067a8159d9527f98630af7d79397a358fcd3 (patch) | |
| tree | 64323d3b5541371f5b2a9e332c8f6174b2798d44 /compiler/rustc_parse/src/errors.rs | |
| parent | 0b31792ef1c15538b07c7b83585dc2fb371c239f (diff) | |
| download | rust-2063067a8159d9527f98630af7d79397a358fcd3.tar.gz rust-2063067a8159d9527f98630af7d79397a358fcd3.zip | |
Fix ub-int-array test for big-endian platforms
As of commit 7767cbb3b0b332fd0a46e347ea7f68f20109d768, the tests/ui/consts/const-eval/ub-int-array.rs test is failing on big-endian platforms (in particular s390x), as the stderr output contains a hex dump that depends on endianness. Since this point intentionally verifies the hex dump to check the uninitialized byte markers, I think we should not simply standardize away the hex dump as is done with some of the other tests in this directory. However, most of the test is already endian-independent. The only exception is one line of hex dump, which can also be made endian-independent by choosing appropriate constants in the source code. Since the 32bit and 64bit stderr outputs were already (and remain) identical, I've merged them and removed the stderr-per-bitwidth marker. Fixes (again) https://github.com/rust-lang/rust/issues/105383.
Diffstat (limited to 'compiler/rustc_parse/src/errors.rs')
0 files changed, 0 insertions, 0 deletions
