Gary Guo
Gary Guo
The reference is introduced in https://github.com/llvm/llvm-project/commit/a4ac434c47434d80bca54bab96f295ed4e972cc6#diff-a380831627112e2516d39595d94e711db7ac63316b9c411aa77af4a561d15ab8
@rustbot label E-needs-bisection
I think that is set by WSLg? WSLd doesn't set DISPLAY for you automatically.
There's prior discussion here: https://rust-lang.zulipchat.com/#narrow/stream/210922-project-ffi-unwind/topic/Behaviour.20of.20destructors.20wrt.20terminate.2Fabort
As pointed out in the discussion, changing how we insert abort to functions is sufficient to change the *observed* behaviour of the implementation, but the key is to decide what's...
Let me explain in greater detail, this'll be long.. For unwinding, there are a few type of cases for nounwind/noexcept/whatever: 1. A stack frame contains no unwind metadata / reaches...
> The problem is, your definition of "being in the process of early termination" requires predicting the future. That goes entirely against the basic principles of an operational semantics, where...
Mostly size cost (landing pads). I guess it doesn't hurt to do a perf run?
Can we document the current behaviour (prefix of frames) for 1.81 in the relnotes and then we further specify that it's all-or-nothing in 1.82?