You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The new short backtrace markers place three frames in backtraces: the
marker initially invoked by downstream code (should be inlined into such
downstream code); the type-erased marker at a known-address (detected by
the backtrace printing code); and the type-restoring callback shim (into
which the actual callback should also be inlined). This differs from
the status-quo ante, where the backtrace markers placed only a single
frame into backtraces.
Whilst these additional frames should have negligible impact on runtime
performance (not only are they called, by the language runtime, at most
twice: once during start before invoking main and once upon panic, if
any; but furthermore, due to the aforementioned inlining, optimized
assembly should be very similar - the additional frames will mostly only
arise from additional debug info), the expected outputs from some miri
tests require updating to reflect these backtrace changes.
0 commit comments