@centril I discovered today that @RalfJ 's PR fixes #64655. Would you be willing to remove your rfcbot concern based on that discovery?
I'll look at this later and see
(I'm happy to add a commit to the PR that encodes a regression test adapted from #64655 ...)
hey @rkruppe or @nagisa , would one of you be able/willing to assist me in dissect why LLVM is behaving this way for this case? I have been unsuccessful thus far in reproducing the situation in a
#![no_core] style test
(that is, I have been trying to simplify things by moving the relevant functionality into its own crate distinct from
core. but when I do so, then the bug with unwind and uncalled-drop disappears)
Can you at least reduce it to just a no_std crate + core?
Yeah I actually got it down to something I was able to dissect
I'll be posting in the bug soon, but I don't think I need help anymore
Ok, glad to hear that
If you are curious, this gist holds my reduced case: https://gist.github.com/425ddc19aa968bbc36b8cb46fab7d15d
(compiling that with
-C opt-level=0 -C lto=fat shows the problem.)
nod nod that looks great