aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Object/Object.cpp
diff options
context:
space:
mode:
authorArtem Dergachev <artem.dergachev@gmail.com>2018-02-15 02:51:58 +0000
committerArtem Dergachev <artem.dergachev@gmail.com>2018-02-15 02:51:58 +0000
commit168e29f6af138ccd1d8919164cae71a15ae735d1 (patch)
treec2c4dfe73ca6ad9984fd1189144cca1b97204768 /llvm/lib/Object/Object.cpp
parent443434e45ce3065024e4895f8dbad5fcae247971 (diff)
downloadllvm-168e29f6af138ccd1d8919164cae71a15ae735d1.zip
llvm-168e29f6af138ccd1d8919164cae71a15ae735d1.tar.gz
llvm-168e29f6af138ccd1d8919164cae71a15ae735d1.tar.bz2
[analyzer] Decide on inlining destructors via EvalCallOptions.
EvalCallOptions were introduced in r324018 for allowing various parts of ExprEngine to notify the inlining mechanism, while preparing for evaluating a function call, of possible difficulties with evaluating the call that they foresee. Then mayInlineCall() would still be a single place for making the decision. Use that mechanism for destructors as well - pass the necessary flags from the CFG-element-specific destructor handlers. Part of this patch accidentally leaked into r324018, which led into a change in tests; this change is reverted now, because even though the change looked correct, the underlying behavior wasn't. Both of these commits were not intended to introduce any function changes otherwise. Differential Revision: https://reviews.llvm.org/D42991 llvm-svn: 325209
Diffstat (limited to 'llvm/lib/Object/Object.cpp')
0 files changed, 0 insertions, 0 deletions