Lines Matching full:specifier
61 /// within the given scope, with optional C++ scope specifier SS, to
86 // nested-name-specifier depends on a template-parameter (14.6.2)
89 // elaborated-type-specifier (7.1.5.3).
126 // nested-name-specifier.
374 "Invalid scope specifier has already been diagnosed");
589 // dependent nested-name-specifier.
763 /// of a declarator's nested name specifier.
1390 // In a given non-class scope, a typedef specifier can be used to
1397 // In a given class scope, a typedef specifier can be used to redefine
1968 /// Declarations using the auto type specifier (C++ [decl.spec.auto]) call back
2083 // For an identifier declared with the storage-class specifier
2147 // For an identifier declared with the storage-class specifier extern in a
2433 // That includes picking up the appropriate access specifier.
2460 llvm_unreachable("unknown storage class specifier");
2479 llvm_unreachable("unknown storage class specifier");
2526 // Recover by removing the storage specifier.
2578 // elaborated-type-specifier inside the anonymous struct or
2596 // Any access specifier is fine.
2948 // Rebuild the scope specifier in-place.
3041 // The user provided a superfluous scope specifier inside a class
3351 // Pretend we didn't see the scope specifier.
3419 /// declares a typedef-name, either using the 'typedef' type specifier or via
3646 // Match up the template parameter lists with the scope specifier, then
3709 // Set the lexical context. If the declarator has a C++ scope specifier, the
4053 static bool FindOverriddenMethod(const CXXBaseSpecifier *Specifier,
4056 RecordDecl *BaseRecord = Specifier->getType()->getAs<RecordType>()->getDecl();
4152 // block scope shall have no explicit storage-class specifier
4351 // scope specifier, or is the object of a friend declaration, the
4355 // Match up the template parameter lists with the scope specifier, then
4426 // All template param lists were matched against the scope specifier:
4442 // The virtual specifier shall only be used in declarations of
4468 // The inline specifier shall not appear on a block scope function declaration.
4479 // The explicit specifier shall be used only in the declaration of a
4526 // Complain about the 'static' specifier if it's on an out-of-line
4699 // A storage-class-specifier shall not be specified in an explicit
4768 // Fake up an access specifier if it's supposed to be a class member.
5120 // C99 6.7.4p4: In a hosted environment, the inline function specifier
5292 // distinguish between a normal initializer and a pure-specifier.
5676 // storage-class specifier or with the storage-class specifier "static",
5812 // for-range-declaration cannot be given a storage class specifier.
6467 // MSVC permits the use of pure specifier (=0) on function definition,
6763 // elaborated-type-specifier shall agree in kind with the
6764 // declaration to which the name in the elaborated-type-specifier
6766 // elaborated-type-specifier that declares a class-name or
6769 // elaborated-type-specifier, the enum keyword shall be used to
6873 // or a scope specifier, which also conveniently avoids this work
6918 // C++0x 7.2p2: The type-specifier-seq of an enum-base shall name an
6990 // nested-name-specifier refers to the current instantiation,
6993 // this as a dependent elaborated-type-specifier.
7077 // -- for an elaborated-type-specifier of the form
7081 // if the elaborated-type-specifier is used in the
7082 // decl-specifier-seq or parameter-declaration-clause of a
7094 // type, including via an elaborated type specifier. We'll
7298 // Use a better diagnostic if an elaborated-type-specifier
7473 // Set the lexical context. If the tag has a C++ scope specifier, the
7485 // Set the access specifier.
7495 // if so, borrow its access specifier.
9049 // enum-specifier, each enumerator has the type of its
9074 // enum-specifier, each enumerator has the type of its
