Displaying 1 result from an estimated 1 matches for "dwarfparser".
2016 Jan 19
5
LLVM libunwind stack usage
...kage that builds and runs exception-using tool at build time. The
failure turned out to be a stack overflow[3] during the forced-unwind
cleanup of a thread with a minimum-sized (4K) stack.
LLVM libunwind has allows for 120 saved registers, common across all
architectures (kMaxRegisterNumber in src/DwarfParser.hpp). In contrast
the GCC unwinder has a target-dependent maximum; on x86-64 it's 18.
LLVM libunwind requires 1920 bytes for register storage, vs. 288 for
the GCC unwinder.
Is it reasonable to change LLVM libunwind to use an approach similar
to GCC's unwinder, and have a target-specific ma...