summaryrefslogtreecommitdiffstats
path: root/llvm/lib/Bitcode/Reader/BitcodeReader.cpp
diff options
context:
space:
mode:
authorDouglas Gregor <dgregor@apple.com>2009-03-10 18:03:33 +0000
committerDouglas Gregor <dgregor@apple.com>2009-03-10 18:03:33 +0000
commit4ea568f213f4771bd2172113b24bec40db3cbf86 (patch)
tree7b9a7ecf00b65ddee861ec25e654d1d228329843 /llvm/lib/Bitcode/Reader/BitcodeReader.cpp
parent156506e749cd053506116146c74b6a7afeb5b01f (diff)
downloadbcm5719-llvm-4ea568f213f4771bd2172113b24bec40db3cbf86.tar.gz
bcm5719-llvm-4ea568f213f4771bd2172113b24bec40db3cbf86.zip
Add a notion of "post-diagnostic hooks", which are callbacks attached
to a diagnostic that will be invoked after the diagnostic (if it is not suppressed). The hooks are allowed to produce additional diagnostics (typically notes) that provide more information. We should be able to use this to help diagnostic clients link notes back to the diagnostic they clarify. Comments welcome; I'll write up documentation and convert other clients (e.g., overload resolution failures) if there are no screams of protest. As the first client of post-diagnostic hooks, we now produce a template instantiation backtrace when a failure occurs during template instantiation. There's still more work to do to make this output pretty, if that's even possible. llvm-svn: 66557
Diffstat (limited to 'llvm/lib/Bitcode/Reader/BitcodeReader.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud