fix real_drop_in_place in comments
This commit is contained in:
parent
b77a7997a8
commit
95934937bb
2 changed files with 2 additions and 2 deletions
|
|
@ -21,7 +21,7 @@ pub fn droppy() {
|
|||
// 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::real_drop_in_place::<drop::SomeUniqueName>`
|
||||
// comment, that's `; call core::intrinsics::drop_in_place::<drop::SomeUniqueName>`
|
||||
// for the `v0` mangling, should switch to matching on that once `legacy` is gone.
|
||||
// CHECK-NOT: invoke void @{{.*}}drop_in_place{{.*}}SomeUniqueName
|
||||
// CHECK: call void @{{.*}}drop_in_place{{.*}}SomeUniqueName
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
// Dropck shouldn't hit a recursion limit from checking `S<u32>` since it has
|
||||
// no free regions or type parameters.
|
||||
// Codegen however, has to error for the infinitely many `real_drop_in_place`
|
||||
// Codegen however, has to error for the infinitely many `drop_in_place`
|
||||
// functions it has been asked to create.
|
||||
// build-fail
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue