summaryrefslogtreecommitdiffstats
path: root/llvm/lib/Target/ARM/Disassembler/ARMDisassembler.cpp
diff options
context:
space:
mode:
authorJordan Rose <jordan_rose@apple.com>2013-05-24 21:43:11 +0000
committerJordan Rose <jordan_rose@apple.com>2013-05-24 21:43:11 +0000
commit56138268b068bfb9a8a0d5448fc9e0ac70ea1b38 (patch)
tree3e21e5acdf71808db086b4564fafd93f86b3547a /llvm/lib/Target/ARM/Disassembler/ARMDisassembler.cpp
parent7291666cd9cb122d313a98784c207922daca0473 (diff)
downloadbcm5719-llvm-56138268b068bfb9a8a0d5448fc9e0ac70ea1b38.tar.gz
bcm5719-llvm-56138268b068bfb9a8a0d5448fc9e0ac70ea1b38.zip
[analyzer] Treat analyzer-synthesized function bodies like implicit bodies.
When generating path notes, implicit function bodies are shown at the call site, so that, say, copying a POD type in C++ doesn't jump you to a header file. This is especially important when the synthesized function itself calls another function (or block), in which case we should try to jump the user around as little as possible. By checking whether a called function has a body in the AST, we can tell if the analyzer synthesized the body, and if we should therefore collapse the call down to the call site like a true implicitly-defined function. <rdar://problem/13978414> llvm-svn: 182677
Diffstat (limited to 'llvm/lib/Target/ARM/Disassembler/ARMDisassembler.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud