2019-10-18 16:47:54 -05:00
|
|
|
// ignore-wasm32-bare compiled with panic=abort by default
|
2023-05-23 08:20:57 -05:00
|
|
|
// needs-unwind - this test verifies the amount of drop calls when unwinding is used
|
2016-02-03 12:27:32 -06:00
|
|
|
// compile-flags: -C no-prepopulate-passes
|
|
|
|
|
|
|
|
#![crate_type = "lib"]
|
|
|
|
|
|
|
|
struct SomeUniqueName;
|
|
|
|
|
|
|
|
impl Drop for SomeUniqueName {
|
2023-10-06 19:29:42 -05:00
|
|
|
#[inline(never)]
|
2016-02-03 12:27:32 -06:00
|
|
|
fn drop(&mut self) {
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2023-10-06 19:29:42 -05:00
|
|
|
#[inline(never)]
|
2016-02-03 12:27:32 -06:00
|
|
|
pub fn possibly_unwinding() {
|
|
|
|
}
|
|
|
|
|
|
|
|
// CHECK-LABEL: @droppy
|
|
|
|
#[no_mangle]
|
|
|
|
pub fn droppy() {
|
|
|
|
// Check that there are exactly 6 drop calls. The cleanups for the unwinding should be reused, so
|
|
|
|
// that's one new drop call per call to possibly_unwinding(), and finally 3 drop calls for the
|
|
|
|
// regular function exit. We used to have problems with quadratic growths of drop calls in such
|
|
|
|
// functions.
|
2019-04-13 11:03:02 -05:00
|
|
|
// FIXME(eddyb) the `void @` forces a match on the instruction, instead of the
|
2021-02-14 15:42:38 -06:00
|
|
|
// comment, that's `; call core::ptr::drop_in_place::<drop::SomeUniqueName>`
|
2019-04-13 11:03:02 -05:00
|
|
|
// for the `v0` mangling, should switch to matching on that once `legacy` is gone.
|
2022-02-18 12:19:30 -06:00
|
|
|
// CHECK-COUNT-6: {{(call|invoke) void @.*}}drop_in_place{{.*}}SomeUniqueName
|
2019-04-13 11:03:02 -05:00
|
|
|
// CHECK-NOT: {{(call|invoke) void @.*}}drop_in_place{{.*}}SomeUniqueName
|
2016-02-03 12:27:32 -06:00
|
|
|
// The next line checks for the } that ends the function definition
|
|
|
|
// CHECK-LABEL: {{^[}]}}
|
|
|
|
let _s = SomeUniqueName;
|
|
|
|
possibly_unwinding();
|
|
|
|
let _s = SomeUniqueName;
|
|
|
|
possibly_unwinding();
|
|
|
|
let _s = SomeUniqueName;
|
|
|
|
possibly_unwinding();
|
|
|
|
}
|