Add a wicked little test-case that illustrates what we have to deal
with to properly support member access expressions in templates. This
test is XFAIL'd, because we get it completely wrong, but I've made the
minimal changes to the representation to at least avoid a crash.
git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@80856 91177308-0d34-0410-b5e6-96231b3b80d8
diff --git a/lib/Sema/SemaCXXScopeSpec.cpp b/lib/Sema/SemaCXXScopeSpec.cpp
index 251ffea..352e553 100644
--- a/lib/Sema/SemaCXXScopeSpec.cpp
+++ b/lib/Sema/SemaCXXScopeSpec.cpp
@@ -357,7 +357,8 @@
// unqualified name lookup in the given scope.
// FIXME: When we're instantiating a template, do we actually have to
- // look in the scope of the template? Seems fishy...
+ // look in the scope of the template? Both EDG and GCC do it; GCC
+ // requires the lookup to be successful, EDG doesn't.
Found = LookupName(S, &II, LookupNestedNameSpecifierName);
ObjectTypeSearchedInScope = true;
}
@@ -366,6 +367,9 @@
// base object type or prior nested-name-specifier, so this
// nested-name-specifier refers to an unknown specialization. Just build
// a dependent nested-name-specifier.
+ if (!Prefix)
+ return NestedNameSpecifier::Create(Context, &II);
+
return NestedNameSpecifier::Create(Context, Prefix, &II);
} else {
// Perform unqualified name lookup in the current scope.