summaryrefslogtreecommitdiffstats
path: root/lldb/source/Plugins/Process/MacOSX-Kernel/ProcessKDP.cpp
diff options
context:
space:
mode:
authorPavel Labath <labath@google.com>2018-05-29 08:16:22 +0000
committerPavel Labath <labath@google.com>2018-05-29 08:16:22 +0000
commit9c3d1f468a0238c5a5a23499bbf76355f5150801 (patch)
tree0cf18c670339ddfdcb3138829791d7af9d430de3 /lldb/source/Plugins/Process/MacOSX-Kernel/ProcessKDP.cpp
parentfa213f797b5c0a0e88cc773ed175a2e594461185 (diff)
downloadbcm5719-llvm-9c3d1f468a0238c5a5a23499bbf76355f5150801.tar.gz
bcm5719-llvm-9c3d1f468a0238c5a5a23499bbf76355f5150801.zip
ManualDWARFIndex: Treat DW_TAG_subprogram and DW_TAG_inlined_subroutine the same way
Summary: We were treating subprograms and inlined subroutines differently when building the index. The difference was in which indexes were individual tags inserted (subprograms went to all indexes, where as inlined subroutines only into the basename and full name indexes). This seems like an error, because an inlined subroutine can still represent an C++ or an ObjC method. I don't see anything in the subprogram branch which should not apply to an inlined subroutine, so I propose to just treat them identically. This makes searching for an inlined method behave the same way as for the apple index. I write an assembly-based test because I did not want to depend on particular clang inlining behavior (and because I wanted to see how hard would it be). Reviewers: clayborg, JDevlieghere Subscribers: eraman, lldb-commits Differential Revision: https://reviews.llvm.org/D47368 llvm-svn: 333398
Diffstat (limited to 'lldb/source/Plugins/Process/MacOSX-Kernel/ProcessKDP.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud