mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Don't use new-llvm-pass-manager=no in test

Browse Source
This commit is contained in:
Nikita Popov 2022-04-19 12:52:48 +02:00
parent e2661bac6d
commit 57717eb8ad
1 changed files with 5 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
src/test/codegen/panic-in-drop-abort.rs
View File

@ -1,10 +1,12 @@
// compile-flags: -Z panic-in-drop=abort -O -Z new-llvm-pass-manager=no // compile-flags: -Z panic-in-drop=abort -O
// ignore-msvc
// Ensure that unwinding code paths are eliminated from the output after // Ensure that unwinding code paths are eliminated from the output after
// optimization. // optimization.
// This test uses -Z new-llvm-pass-manager=no, because the expected optimization does not happen // This test uses ignore-msvc, because the expected optimization does not happen on targets using
// on targets using SEH exceptions (i.e. MSVC) anymore. The core issue is that Rust promises that // SEH exceptions with the new LLVM pass manager anymore, see
// https://github.com/llvm/llvm-project/issues/51311. The core issue is that Rust promises that
// the drop_in_place() function can't unwind, but implements it in a way that *can*, because we // the drop_in_place() function can't unwind, but implements it in a way that *can*, because we
// currently go out of our way to allow longjmps, which also use the unwinding mechanism on MSVC // currently go out of our way to allow longjmps, which also use the unwinding mechanism on MSVC
// targets. We should either forbid longjmps, or not assume nounwind, making this optimization // targets. We should either forbid longjmps, or not assume nounwind, making this optimization