rust/tests/ui/issues/issue-29485.rs

//@ run-pass
#![allow(unused_attributes)]
//@ aux-build:issue-29485.rs
//@ needs-unwind
//@ needs-threads

#[feature(recover)]

extern crate a;

fn main() {
    let _ = std::thread::spawn(move || {
        a::f(&mut a::X(0), g);
    }).join();
}

fn g() {
    panic!();
}
Add `// run-pass` annotations to all the tests under `ui/run-pass/`. (I may have accidentally added it to some auxilliary crates as well; my emacs-macro-based methodology was pretty crude.) 2018-08-30 14:18:55 +02:00			`//@ run-pass`
Add `#![allow(..)]` as necessary to get re-migrated run-pass tests compiling with clean stderr again. Most were added mechanically. 2018-09-25 23:51:35 +02:00			`#![allow(unused_attributes)]`
Workaround LLVM optimizer bug by not marking &mut pointers as noalias LLVM's memory dependence analysis doesn't properly account for calls that could unwind and thus effectively act as a branching point. This can lead to stores that are only visible when the call unwinds being removed, possibly leading to calls to drop() functions with b0rked memory contents. As there is no fix for this in LLVM yet and we want to keep compatibility to current LLVM versions anyways, we have to workaround this bug by omitting the noalias attribute on &mut function arguments. Benchmarks suggest that the performance loss by this change is very small. Thanks to @RalfJung for pushing me towards not removing too many noalias annotations and @alexcrichton for helping out with the test for this bug. Fixes #29485 2016-01-29 11:11:24 +01:00			`//@ aux-build:issue-29485.rs`
Add needs-unwind to tests that depend on panicking This directive isn't automatically set by compiletest or x.py, but can be turned on manually for targets that require it. 2021-12-03 15:32:51 +00:00			`//@ needs-unwind`
tests: use `needs-threads` instead of `ignore-emscripten` 2025-01-23 17:05:01 +08:00			`//@ needs-threads`
Workaround LLVM optimizer bug by not marking &mut pointers as noalias LLVM's memory dependence analysis doesn't properly account for calls that could unwind and thus effectively act as a branching point. This can lead to stores that are only visible when the call unwinds being removed, possibly leading to calls to drop() functions with b0rked memory contents. As there is no fix for this in LLVM yet and we want to keep compatibility to current LLVM versions anyways, we have to workaround this bug by omitting the noalias attribute on &mut function arguments. Benchmarks suggest that the performance loss by this change is very small. Thanks to @RalfJung for pushing me towards not removing too many noalias annotations and @alexcrichton for helping out with the test for this bug. Fixes #29485 2016-01-29 11:11:24 +01:00
			`#[feature(recover)]`

			`extern crate a;`

			`fn main() {`
			`let _ = std::thread::spawn(move \|\| {`
			`a::f(&mut a::X(0), g);`
			`}).join();`
			`}`

			`fn g() {`
			`panic!();`
			`}`