rust/tests/ui/limits/huge-array-simple-64.rs

// FIXME(#61117): Remove revisions once x86_64-gnu-debug CI job sets rust.debuginfo-level-tests=2
// NOTE: The .stderr for both revisions shall be identical.
//@ revisions: no-debuginfo full-debuginfo
//@[no-debuginfo] compile-flags: -Cdebuginfo=0
//@[full-debuginfo] compile-flags: -Cdebuginfo=2
//@ build-fail
//@ ignore-32bit

#![allow(arithmetic_overflow)]

fn main() {
    let _fat: [u8; (1<<61)+(1<<31)] = //~ ERROR too big for the target architecture
        [0; (1u64<<61) as usize +(1u64<<31) as usize];
}
compiler: Include span of too huge array with `-Cdebuginfo=2` We have a few ui tests to ensure we emit an error if we encounter too big arrays. Before this fix, compiling the tests with `-Cdebuginfo=2` would not include the spans of the instantiation sites, because the error is then emitted from a different code path that does not include the span. Propagate the span to the error also in the debuginfo case, so the tests passes regardless of debuginfo level. 2025-08-30 10:38:23 +02:00			`// FIXME(#61117): Remove revisions once x86_64-gnu-debug CI job sets rust.debuginfo-level-tests=2`
			`// NOTE: The .stderr for both revisions shall be identical.`
			`//@ revisions: no-debuginfo full-debuginfo`
			`//@[no-debuginfo] compile-flags: -Cdebuginfo=0`
			`//@[full-debuginfo] compile-flags: -Cdebuginfo=2`
[AUTO-GENERATED] Migrate ui tests from `//` to `//@` directives 2024-02-16 20:02:50 +00:00			`//@ build-fail`
			`//@ ignore-32bit`
fix tests 2019-08-04 21:18:05 -07:00
better lint names 2020-02-18 22:49:47 +01:00			`#![allow(arithmetic_overflow)]`
fix tests 2019-08-04 21:18:05 -07:00
			`fn main() {`
TL note: current means target 2024-09-20 00:39:10 -07:00			`let _fat: [u8; (1<<61)+(1<<31)] = //~ ERROR too big for the target architecture`
review comments 2019-08-06 11:23:32 -07:00			`[0; (1u64<<61) as usize +(1u64<<31) as usize];`
fix tests 2019-08-04 21:18:05 -07:00			`}`