Lines Matching refs:within

49   headers stored within the PCH file.  Thus, a precompiled header design
130 within `LLVM's bitstream format <http://llvm.org/docs/BitCodeFormat.html>`_.
177   is stored within the :ref:`pchinternals-sourcemgr`, but its contents are
197 column/line positions within a source file or macro instantiation.  The AST
206 maps file IDs to the position within the AST file where the information about
238 When types are deserialized from the AST file, the data within the record is
246 an associated mapping from the user-defined types block to the location within
248 enabling lazy deserialization of types.  When a type is referenced from within
262 within the record is used to build and populate a new instance of the
264 numeric ID that is used to refer to that declaration within the AST file.  In
266 within the precompiled header where that declaration is described.
273 and so on.  Within Clang, each declaration is stored within a :ref:`declaration
275 Declaration contexts provide the mechanism to perform name lookup within a
277 iterate over the declarations stored within a context (e.g., iterate over all
282 declarations stored within that declaration context.  Therefore, Clang will
284 declarations within that translation unit.  When required, the declarations
285 stored within a declaration context will be deserialized.  There are two
286 representations of the declarations within a declaration context, which
289 * When the front end performs name lookup to find a name ``x`` within a given
292   refers to an on-disk hash table that maps from the names within that
296 * When the front end performs iteration over all of the declarations within a
320 that statement or expression.  Each substatement or subexpression within an
356 identifier mentioned within the AST file to the serialized representation of
363 * If the identifier names a macro, the offset of the macro definition within
379 value (the identifier ID) to the location within the on-disk hash table where
393 stores all of the selectors used by entities within the AST file.  The design
402 As with identifiers, selectors are represented by numeric values within the AST
404 selector within the on-disk hash table, and will be used when de-serializing an
431   been seen.  In this case, the AST reader searches for this identifier within
440   required, and read the declarations stored within a declaration context