summaryrefslogtreecommitdiffstats
path: root/llvm/lib/Bitcode
diff options
context:
space:
mode:
authorEnrico Granata <egranata@apple.com>2013-10-30 23:46:27 +0000
committerEnrico Granata <egranata@apple.com>2013-10-30 23:46:27 +0000
commit686f3deb446b6b6a62d9f4a4611859fab0c8a78c (patch)
tree437367f96e2158b7c7790ff15ad955980df5ddda /llvm/lib/Bitcode
parent909d0c063f54ac10d01dcd0c80199e0c826e4ab7 (diff)
downloadbcm5719-llvm-686f3deb446b6b6a62d9f4a4611859fab0c8a78c.tar.gz
bcm5719-llvm-686f3deb446b6b6a62d9f4a4611859fab0c8a78c.zip
This checkin introduces the notion of hardcoded formatters, which LLDB can bind to a ValueObject internally depending on any criteria
User-vended by-type formatters still would prevail on these hardcoded ones For the time being, while the infrastructure is there, no such formatters exist This can be useful for cases such as expanding vtables for C++ class pointers, when there is no clear cut notion of a typename matching, and the feature is low-level enough that it makes sense for the debugger core to be vending it llvm-svn: 193724
Diffstat (limited to 'llvm/lib/Bitcode')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud