summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/expression_command/call-function/main.cpp
diff options
context:
space:
mode:
authorGeorge Burgess IV <george.burgess.iv@gmail.com>2016-05-25 22:31:54 +0000
committerGeorge Burgess IV <george.burgess.iv@gmail.com>2016-05-25 22:31:54 +0000
commit8c892b556f5c0dbc55434401faae846ab376e4bc (patch)
tree0f933c2f916032d8e4cd6fc9042f4f723fb03ae6 /lldb/packages/Python/lldbsuite/test/expression_command/call-function/main.cpp
parent1b356bf8984fe1b716ddd1799d629eb69a280a69 (diff)
downloadbcm5719-llvm-8c892b556f5c0dbc55434401faae846ab376e4bc.tar.gz
bcm5719-llvm-8c892b556f5c0dbc55434401faae846ab376e4bc.zip
[Sema] Note when we encounter a problem in ExprConstant.
Currently, the constexpr evaluator is very conservative about unmodeled side-effects when we're evaluating an expression in a mode that allows such side-effects. This patch makes us note when we might have actually encountered an unmodeled side-effect, which allows us to be more accurate when we know an unmodeled side-effect couldn't have occurred. This patch has been split into two commits; this one primarily introduces the bits necessary to track whether we might have potentially hit such a side-effect. The one that actually does the tracking (which boils down to more or less a rename of keepEvaluatingAfterFailure to noteFailure) is coming soon. Differential Revision: http://reviews.llvm.org/D18540 llvm-svn: 270781
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/expression_command/call-function/main.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud