File: drop.rs

package info (click to toggle)
rustc 1.85.0%2Bdfsg3-1
  • links: PTS, VCS
  • area: main
  • in suites: experimental, sid, trixie
  • size: 893,396 kB
  • sloc: xml: 158,127; python: 35,830; javascript: 19,497; cpp: 19,002; sh: 17,245; ansic: 13,127; asm: 4,376; makefile: 1,051; perl: 29; lisp: 29; ruby: 19; sql: 11
file content (36 lines) | stat: -rw-r--r-- 1,362 bytes parent folder | download | duplicates (3)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
//@ needs-unwind - this test verifies the amount of drop calls when unwinding is used
//@ compile-flags: -C no-prepopulate-passes

#![crate_type = "lib"]

struct SomeUniqueName;

impl Drop for SomeUniqueName {
    #[inline(never)]
    fn drop(&mut self) {}
}

#[inline(never)]
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.
    // FIXME(eddyb) the `void @` forces a match on the instruction, instead of the
    // comment, that's `; call core::ptr::drop_in_place::<drop::SomeUniqueName>`
    // for the `v0` mangling, should switch to matching on that once `legacy` is gone.
    // CHECK-COUNT-6: {{(call|invoke) void @.*}}drop_in_place{{.*}}SomeUniqueName
    // CHECK-NOT: {{(call|invoke) void @.*}}drop_in_place{{.*}}SomeUniqueName
    // 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();
}