about summary refs log tree commit diff
diff options
context:
space:
mode:
authorNikita Popov <npopov@redhat.com>2022-04-19 16:12:23 +0200
committerNikita Popov <npopov@redhat.com>2022-04-20 09:25:47 +0200
commit3cf0809a8d3ce66f468eed3dea96408d42eec33b (patch)
treec726b6ead89250fb5969f5c82b9e582a5e272bdc
parent890cabac8acb566dee2d01bdfd9198546adfa310 (diff)
downloadrust-3cf0809a8d3ce66f468eed3dea96408d42eec33b.tar.gz
rust-3cf0809a8d3ce66f468eed3dea96408d42eec33b.zip
Drop inaccurate comment
The linked issue has an accurate description of the situation,
drop the inaccurate comment.
-rw-r--r--src/test/codegen/panic-in-drop-abort.rs6
1 files changed, 1 insertions, 5 deletions
diff --git a/src/test/codegen/panic-in-drop-abort.rs b/src/test/codegen/panic-in-drop-abort.rs
index 7b9c41b658a..7a84484c419 100644
--- a/src/test/codegen/panic-in-drop-abort.rs
+++ b/src/test/codegen/panic-in-drop-abort.rs
@@ -6,11 +6,7 @@
 
 // This test uses ignore-msvc, because the expected optimization does not happen on targets using
 // 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
-// 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
-// incompatible with the current behavior of running cleanuppads on longjmp unwinding.
+// https://github.com/llvm/llvm-project/issues/51311.
 
 // CHECK-NOT: {{(call|invoke).*}}should_not_appear_in_output