Home | History | Annotate | Download | only in docs

Lines Matching full:identifier

228 :ref:`identifier table <pchinternals-ident-table>`.
352 Identifier Table Block
355 The identifier table block contains an on-disk hash table that maps each
356 identifier mentioned within the AST file to the serialized representation of
357 the identifier's information (e.g, the ``IdentifierInfo`` structure). The
360 * The actual identifier string.
361 * Flags that describe whether this identifier is the name of a built-in, a
362 poisoned identifier, an extension token, or a macro.
363 * If the identifier names a macro, the offset of the macro definition within
365 * If the identifier names one or more declarations visible from translation
370 into the identifier table as an external lookup source. Thus, when the user
371 program refers to an identifier that has not yet been seen, Clang will perform
372 a lookup into the identifier table. If an identifier is found, its contents
379 value (the identifier ID) to the location within the on-disk hash table where
380 that identifier is stored. This mapping is used when deserializing the name of
381 a declaration, the identifier of a token, or any other construct in the AST
394 of the method pool is similar to that of the :ref:`identifier table
430 is used whenever the program source refers to an identifier that has not yet
431 been seen. In this case, the AST reader searches for this identifier within
432 its :ref:`identifier table <pchinternals-ident-table>` to load any top-level
433 declarations or macros associated with that identifier.
495 :ref:`identifier table <pchinternals-ident-table>`: the search starts at the
497 to the identifier table in the precompiled header it depends on, and so one.