rust/tests/ui/layout/valid_range_oob.rs

//@ failure-status: 101
//@ normalize-stderr: "note: .*\n\n" -> ""
//@ normalize-stderr: "thread 'rustc'.*panicked.*\n" -> ""
//@ rustc-env:RUST_BACKTRACE=0

#![feature(rustc_attrs)]

#[rustc_layout_scalar_valid_range_end(257)]
struct Foo(i8);

// Need to do in a constant, as runtime codegen
// does not compute the layout of `Foo` in check builds.
const FOO: Foo = unsafe { Foo(1) };

fn main() {}
Add a test for OOB ranges 2022-11-07 10:26:23 +00:00			`//@ failure-status: 101`
Remove the `-test` suffix from normalize directives 2024-12-25 22:12:17 +11:00			`//@ normalize-stderr: "note: .*\n\n" -> ""`
Print thread ID in panic message if thread name is unknown `panic!` does not print any identifying information for threads that are unnamed. However, in many cases, the thread ID can be determined. This changes the panic message from something like this: thread '<unnamed>' panicked at src/main.rs:3:5: explicit panic To something like this: thread '<unnamed>' (0xff9bf) panicked at src/main.rs:3:5: explicit panic Stack overflow messages are updated as well. This change applies to both named and unnamed threads. The ID printed is the OS integer thread ID rather than the Rust thread ID, which should also be what debuggers print. 2023-09-11 00:59:31 -04:00			`//@ normalize-stderr: "thread 'rustc'.panicked.\n" -> ""`
Add a test for OOB ranges 2022-11-07 10:26:23 +00:00			`//@ rustc-env:RUST_BACKTRACE=0`

			`#![feature(rustc_attrs)]`

			`#[rustc_layout_scalar_valid_range_end(257)]`
			`struct Foo(i8);`

			`// Need to do in a constant, as runtime codegen`
			// does not compute the layout of `Foo` in check builds.
			`const FOO: Foo = unsafe { Foo(1) };`

			`fn main() {}`