Displaying 2 results from an estimated 2 matches for "1m26s".
Did you mean:
126s
2019 Jan 11
2
Slow debugger starts of LLVM tools
Yep, as others have mentioned - using a linker-generated gdb-index is super
helpful (10s for my machine to start debugging an unoptimized clang, set a
breakpoint at llvm::StringRef::StringRef and run until that breakpoint is
hit, as opposed to 1m26s without an index)
That's also with/without split DWARF too, but I suspect most of the benefit
is in the index there. Split DWARF might save you some linking time and
/maybe/ some debugger performance.
On Thu, Jan 10, 2019 at 1:16 PM Petr Penzin via llvm-dev <
llvm-dev at lists.llvm.org>...
2019 Jan 10
2
Slow debugger starts of LLVM tools
This is admittedly a longshot, but Can you check whether you experience
unusually long run times with LLDB? If there’s something strange about tge
binaries we generate, maybe lldb will exhibit some strangeness too and we
can more easily profile it.
On Wed, Jan 9, 2019 at 2:48 PM Shoaib Meenai via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> I don't know about the issues with