Commit 0e1066e6 authored by Bill Wendling's avatar Bill Wendling
Browse files

---Merging r196453

    Parse: Recover better from bad definitions with base specifiers
    
    We would skip until the next comma, hoping good things whould lie there,
    however this would fail when we have such things as this:
    
    struct A {};
    template <typename>
    struct D;
    template <>
    struct D<C> : B, A::D;
    
    Once this happens, we would believe that D with a nested namespace
    specifier of A was a variable that was being declared. We would go on
    to complain that there was an extraneous 'template <>' on their variable
    declaration.
    
    Crashes would happen when 'A' gets defined as 'enum class A {}' as
    various asserts would fire.
    
    Instead, we should skip up until the semicolon if we see that we are in
    the middle of a definition and the current token is a ':'
    
    This fixes PR17084.

llvm-svn: 197905
parent 04501dbc
Loading
Loading
Loading
Loading
+7 −1
Original line number Diff line number Diff line
@@ -1427,6 +1427,12 @@ void Parser::ParseClassSpecifier(tok::TokenKind TagTokKind,
        << DeclSpec::getSpecifierName(TagType);
    }

    // If we are parsing a definition and stop at a base-clause, continue on
    // until the semicolon.  Continuing from the comma will just trick us into
    // thinking we are seeing a variable declaration.
    if (TUK == Sema::TUK_Definition && Tok.is(tok::colon))
      SkipUntil(tok::semi, StopBeforeMatch);
    else
      SkipUntil(tok::comma, StopAtSemi);
    return;
  }
+6 −0
Original line number Diff line number Diff line
@@ -119,3 +119,9 @@ void MissingSemiInFunction() {
  struct Inner4 {} // ok, no missing ';' here
  Inner5;
}

namespace PR17084 {
enum class EnumID {};
template <typename> struct TempID;
template <> struct TempID<BadType> : BadType, EnumID::Garbage; // expected-error{{use of undeclared identifier 'BadType'}}
}