summaryrefslogtreecommitdiffstats
path: root/clang/lib/CodeGen/CodeGenModule.cpp
diff options
context:
space:
mode:
authorFaisal Vali <faisalv@yahoo.com>2013-11-12 03:48:27 +0000
committerFaisal Vali <faisalv@yahoo.com>2013-11-12 03:48:27 +0000
commit8bc2bc71f6741ed867a9df33269e5fd59009e1ce (patch)
treee68c654dd55b3d0150322ca008e09057b80acab6 /clang/lib/CodeGen/CodeGenModule.cpp
parentc1a13f3f20b808a220d84ad88b9145b90045898c (diff)
downloadbcm5719-llvm-8bc2bc71f6741ed867a9df33269e5fd59009e1ce.tar.gz
bcm5719-llvm-8bc2bc71f6741ed867a9df33269e5fd59009e1ce.zip
A quick fix to PR17877 that was introduced by r194188 (generic-lambda-capturing) that broke libc++.
See http://lists.cs.uiuc.edu/pipermail/cfe-dev/2013-November/033369.html for discussion on cfe-dev. This fix explicitly checks whether we are within the declcontext of a lambda's call operator - which is what I had intended to be true (and assumed would be true if getCurLambda returns a valid pointer) before checking whether a lambda can capture the potential-captures of the innermost lambda. A deeper fix (that addresses why getCurLambda() returns a valid pointer when perhaps it shouldn't?) - as proposed by Richard Smith in http://llvm.org/bugs/show_bug.cgi?id=17877 - has been suggested as a FIXME. Patch was LGTM'd by Richard (just barely :) http://llvm-reviews.chandlerc.com/D2144 llvm-svn: 194448
Diffstat (limited to 'clang/lib/CodeGen/CodeGenModule.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud