diff options
| author | Weihang Lo <weihanglo@users.noreply.github.com> | 2023-08-24 22:54:00 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-08-24 22:54:00 +0100 |
| commit | c99619752594c0c37a30b32fc79e49bd8e7bc0fe (patch) | |
| tree | dfb1013ba3dc3d8ccd76ac24aba0278cd4a52c7a /compiler/rustc_parse/src/errors.rs | |
| parent | d417ae5fdadb34a760a7cf893e5f67a49dce6df8 (diff) | |
| parent | 2063067a8159d9527f98630af7d79397a358fcd3 (diff) | |
| download | rust-c99619752594c0c37a30b32fc79e49bd8e7bc0fe.tar.gz rust-c99619752594c0c37a30b32fc79e49bd8e7bc0fe.zip | |
Rollup merge of #115167 - uweigand:ubintarray-endian-fix, r=RalfJung
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