Home | History | Annotate | Download | only in Sema

Lines Matching refs:Specifier

85 /// \brief Determine whether the token kind starts a simple-type-specifier.
89 // token kind is a valid type specifier
125 /// within the given scope, with optional C++ scope specifier SS, to
152 // nested-name-specifier depends on a template-parameter (14.6.2)
155 // elaborated-type-specifier (7.1.5.3).
192 // nested-name-specifier.
318 // constructor or destructor name (in such a case, the scope specifier
494 "Invalid scope specifier has already been diagnosed");
571 /// Build a ParsedType for a simple-type-specifier with a nested-name-specifier.
732 // dependent nested-name-specifier.
927 /// of a declarator's nested name specifier.
1744 // In a given non-class scope, a typedef specifier can be used to
1751 specifier can be used to redefine
1856 /// special semantics of C11's _Alignas specifier and C++11's alignas attribute.
1935 // if any declaration of an entity has an alignment-specifier,
1940 // specifier, any other declaration of that object shall also
1941 // have no alignment specifier.
2063 // if any declaration of an entity has an alignment-specifier,
2068 // specifier, any other declaration of that object shall also
2069 // have no alignment specifier.
2773 /// Declarations using the auto type specifier (C++ [decl.spec.auto]) call back
2886 // For an identifier declared with the storage-class specifier
2958 // For an identifier declared with the storage-class specifier extern in a
3061 // nested-name-specifier unless it is an explicit instantiation
3073 // Track whether this decl-specifier declares anything.
3140 // unnamed bit-field, the decl-specifier-seq shall introduce one or more
3151 // If a storage-class-specifier appears in a decl-specifier-seq, [...] the
3154 // If a cv-qualifier appears in a decl-specifier-seq, the
3307 // That includes picking up the appropriate access specifier.
3334 llvm_unreachable("unknown storage class specifier");
3353 llvm_unreachable("unknown storage class specifier");
3403 // Recover by removing the storage specifier.
3459 // elaborated-type-specifier inside the anonymous struct or
3484 // Any access specifier is fine.
3869 // Rebuild the scope specifier in-place.
3910 /// nested-name-specifier.
3912 /// \param SS The nested-name-specifier of the declarator-id.
3914 /// \param DC The declaration context to which the nested-name-specifier
3938 // The user provided a superfluous scope specifier that refers back to the
3990 // [...] "The nested-name-specifier of the qualified declarator-id shall
4145 // the nested-name-specifier of the declarator-id.
4407 // Pretend we didn't see the scope specifier.
4479 /// declares a typedef-name, either using the 'typedef' type specifier or via
4786 // Match up the template parameter lists with the scope specifier, then
4843 // Set the lexical context. If the declarator has a C++ scope specifier, the
5256 static bool FindOverriddenMethod(const CXXBaseSpecifier *Specifier,
5259 RecordDecl *BaseRecord = Specifier->getType()->getAs<RecordType>()->getDecl();
5571 // block scope shall have no explicit storage-class specifier
5846 // scope specifier, or is the object of a friend declaration, the
5850 // Match up the template parameter lists with the scope specifier, then
5931 // All template param lists were matched against the scope specifier:
5947 // The virtual specifier shall only be used in declarations of
5973 // The inline specifier shall not appear on a block scope function
5985 // The explicit specifier shall be used only in the declaration of a
6071 // Complain about the 'static' specifier if it's on an out-of-line
6304 // A storage-class-specifier shall not be specified in an explicit
6387 // Fake up an access specifier if it's supposed to be a class member.
6658 // A constexpr specifier for a non-static member function that is not
6857 // C11 6.7.4p4: In a hosted environment, no function specifier(s) shall
7168 // distinguish between a normal initializer and a pure-specifier.
7474 // with the constexpr specifier; if so, its declaration shall specify a
7645 // the constexpr specifier; if so, its declaration shall specify
7647 // C++11 [dcl.constexpr]p1: The constexpr specifier shall be applied only to
7701 // storage-class specifier or with the storage-class specifier "static",
7839 // for-range-declaration cannot be given a storage class specifier.
8752 // MSVC permits the use of pure specifier (=0) on function definition,
9217 // elaborated-type-specifier shall agree in kind with the
9218 // declaration to which the name in the elaborated-type-specifier
9220 // elaborated-type-specifier that declares a class-name or
9223 // elaborated-type-specifier, the enum keyword shall be used to
9331 // or a scope specifier, which also conveniently avoids this work
9377 // C++0x 7.2p2: The type-specifier-seq of an enum-base shall name an
9444 // nested-name-specifier refers to the current instantiation,
9447 // this as a dependent elaborated-type-specifier.
9532 // -- for an elaborated-type-specifier of the form
9536 // if the elaborated-type-specifier is used in the
9537 // decl-specifier-seq or parameter-declaration-clause of a
9549 // type, including via an elaborated type specifier. We'll
9651 // If this is an elaborated-type-specifier for a scoped enumeration,
9757 // Use a better diagnostic if an elaborated-type-specifier
9891 // nested-name-specifier against the current context. We don't do this
9955 // Set the lexical context. If the tag has a C++ scope specifier, the
9967 // Set the access specifier.
9977 // if so, borrow its access specifier.
11709 // enum-specifier, each enumerator has the type of its
11734 // enum-specifier, each enumerator has the type of its