summaryrefslogtreecommitdiffstats
path: root/llvm
diff options
context:
space:
mode:
authorJohn McCall <rjmccall@apple.com>2009-11-22 02:49:43 +0000
committerJohn McCall <rjmccall@apple.com>2009-11-22 02:49:43 +0000
commita9ee325d719647a2bdee249d300153a9fc1753ee (patch)
tree5cd58202b83b4584d0d9064f03c5cbe1167d0f66 /llvm
parent663e0a06b02647e39fb3997a8cbfacab2e36760e (diff)
downloadbcm5719-llvm-a9ee325d719647a2bdee249d300153a9fc1753ee.tar.gz
bcm5719-llvm-a9ee325d719647a2bdee249d300153a9fc1753ee.zip
If a C++ qualified id is followed by a postfix suffix, it is never the direct
operand of an addressof operator, and so we should not treat it as an abstract member-pointer expression and therefore suppress the implicit member access. This is really a well-formedness constraint on expressions: a DeclRefExpr of a FieldDecl or a non-static CXXMethodDecl (or template thereof, or unresolved collection thereof) should not be allowed in an arbitrary location in the AST. Arguably it shouldn't be allowed anywhere and we should have a different expr node type for this. But unfortunately we don't have a good way of enforcing this kind of constraint right now. llvm-svn: 89578
Diffstat (limited to 'llvm')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud