diff options
| author | Jaroslav Sevcik <jarin@google.com> | 2020-03-20 11:39:30 +0100 |
|---|---|---|
| committer | Pavel Labath <pavel@labath.sk> | 2020-03-20 11:41:56 +0100 |
| commit | 089cfe113da1395427dd31f21067d5b618b89d7c (patch) | |
| tree | f556fa39c8be25319fc16596e84a9b6a1a7b05c3 /clang/unittests/Tooling/Syntax/TreeTest.cpp | |
| parent | 63778bc653a2193717b39874e9f69dcfe3f8771c (diff) | |
| download | llvm-089cfe113da1395427dd31f21067d5b618b89d7c.zip llvm-089cfe113da1395427dd31f21067d5b618b89d7c.tar.gz llvm-089cfe113da1395427dd31f21067d5b618b89d7c.tar.bz2 | |
Improve step over performance
Summary:
This patch improves step over performance for the case when we are
stepping over a call with a next-branch-breakpoint (see
https://reviews.llvm.org/D58678), and we encounter a stop during the
call. Currently, this causes the thread plan to step-out //each frame//
until it reaches the step-over range. This is a regression introduced by
https://reviews.llvm.org/D58678 (which did improve other things!). Prior
to that change, the step-over plan would always step-out just once.
With this patch, if we find ourselves stopped in a deeper stack frame
and we already have a next branch breakpoint, we simply return from the
step-over plan's ShouldStop handler without pushing the step out plan.
In my experiments this improved the time of stepping over a call that
loads 12 dlls from 14s to 5s. This was in remote debugging scenario with
10ms RTT, the call in question was Vulkan initialization
(vkCreateInstance), which loads various driver dlls. Loading those dlls
must stop on the rendezvous breakpoint, causing the perf problem
described above.
Reviewers: clayborg, labath, jingham
Reviewed By: jingham
Subscribers: lldb-commits
Tags: #lldb
Differential Revision: https://reviews.llvm.org/D76216
Diffstat (limited to 'clang/unittests/Tooling/Syntax/TreeTest.cpp')
0 files changed, 0 insertions, 0 deletions