summaryrefslogtreecommitdiffstats
path: root/clang/lib/Frontend/CompilerInvocation.cpp
diff options
context:
space:
mode:
authorJordan Rose <jordan_rose@apple.com>2013-02-22 01:51:15 +0000
committerJordan Rose <jordan_rose@apple.com>2013-02-22 01:51:15 +0000
commit5772f82d1eaf8284fe2f2d637282091a484c13a4 (patch)
treea0c1b8bbdfdb097d5f5c03907d0798d20cdb5392 /clang/lib/Frontend/CompilerInvocation.cpp
parent047f81a5dfe84dab8968f7f45a401bd643b27dd8 (diff)
downloadbcm5719-llvm-5772f82d1eaf8284fe2f2d637282091a484c13a4.tar.gz
bcm5719-llvm-5772f82d1eaf8284fe2f2d637282091a484c13a4.zip
[analyzer] Make sure a materialized temporary matches its bindings.
This is a follow-up to r175830, which made sure a temporary object region created for, say, a struct rvalue matched up with the initial bindings being stored into it. This does the same for the case in which the AST actually tells us that we need to create a temporary via a MaterializeObjectExpr. I've unified the two code paths and moved a static helper function onto ExprEngine. This also caused a bit of test churn, causing us to go back to describing temporary regions without a 'const' qualifier. This seems acceptable; it's our behavior from a few months ago. <rdar://problem/13265460> (part 2) llvm-svn: 175854
Diffstat (limited to 'clang/lib/Frontend/CompilerInvocation.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud