[llvm-dev] [RFC] Propeller: A frame work for Post Link Optimizations
Krzysztof Pszeniczny via llvm-dev
llvm-dev at lists.llvm.org
Wed Oct 2 12:19:43 PDT 2019
On Wed, Oct 2, 2019 at 8:41 PM Maksim Panchenko via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> *Pessimization/overhead for stack unwinding used by system-wide profilers
> for exception handling*
> Larger CFI programs put an extra burden on unwinding at runtime as more CFI
> (and thus native) instructions have to be executed. This will cause more
> overhead for any profiler that records stack traces, and, as you correctly
> in the proposal, for any program that heavily uses exceptions.
The number of CFI instructions that have to be executed when unwinding any
given stack stays the same. The CFI instructions for a function have to be
duplicated in every basic block section, but when performing unwinding only
one such a set is executed -- the copy for the current basic block.
However, this copy contains precisely the same CFI instructions as the ones
that would have to be executed if there were no basic block sections.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the llvm-dev