summaryrefslogtreecommitdiffstats
path: root/clang/lib/Frontend/ModuleDependencyCollector.cpp
diff options
context:
space:
mode:
authorJim Ingham <jingham@apple.com>2016-05-06 23:44:10 +0000
committerJim Ingham <jingham@apple.com>2016-05-06 23:44:10 +0000
commit9b8eb155d8a47344fd2b60d4a74bb427703d8ab8 (patch)
tree2a0642855a068b0c67de73307f4eb177ec157a78 /clang/lib/Frontend/ModuleDependencyCollector.cpp
parent1ed1aeaa94061a9007df291e44a4407958d54223 (diff)
downloadbcm5719-llvm-9b8eb155d8a47344fd2b60d4a74bb427703d8ab8.tar.gz
bcm5719-llvm-9b8eb155d8a47344fd2b60d4a74bb427703d8ab8.zip
Fix the way the ShouldStopHere checker handles the general case of "stepping through line 0 code".
That's good 'cause it means all the different kinds of source line stepping won't leave user in the middle of compiler implementation code or code inlined from odd places, etc. But it turns out that the compiler also marks functions it MIGHT inline as all being of line 0. That would mean we single step through this code instead of just stepping out. That is both inefficient, and more error prone 'cause these little nuggets tend to be bits of hand-written assembly and the like and are hard to step through. This change just checks and if the entire function is marked with line 0, we step out rather than step through. <rdar://problem/25966460> llvm-svn: 268823
Diffstat (limited to 'clang/lib/Frontend/ModuleDependencyCollector.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud