Lines Matching refs:records

230 Data records consist of a record code and a number of (up to) 64-bit integer
267 encoded according to the `abbreviation definition`_.  This allows records to be
268 encoded significantly more densely than records encoded with the
283 to specify a dense encoding for a class of records once, then use that encoding
284 to emit many records.  It takes space to emit the encoding into the file, but
285 the space is recouped (hopefully plus some) when the records that use it are
311 records reference this ID to indicate what abbreviation they are invoking.
381 #. The second value, 2, is the record code for ``TRIPLE`` records within LLVM IR
411 The currently specified records are:
421 ``SETBID`` records can occur multiple times throughout the block to change which
423 other records.
425 Standard ``DEFINE_ABBREV`` records can occur inside ``BLOCKINFO`` blocks, but
441 the abbreviations they contain are essential for parsing records from the
470 LLVM IR is encoded into a bitstream by defining blocks and records.  It uses
472 records for things like instructions, global variable descriptors, type
509 ``CST_CODE_WIDE_INTEGER`` records within ``CONSTANTS_BLOCK`` blocks.
534 * 16 --- `METADATA_ATTACHMENT`_ --- This contains records associating metadata
543 and each bitcode file must contain exactly one. In addition to records
599 variable or function ``section`` attributes) within the module. These records
601 or ``FUNCTION`` records.
738 by ``GLOBALVAR``, ``FUNCTION``, and ``ALIAS`` records.  After a ``PURGEVALS``
751 ``gc`` attributes within the module. These records can be referenced by 1-based
752 index in the *gc* fields of ``FUNCTION`` records.
761 in the *paramattr* field of module block `FUNCTION`_ records, or within the
762 *attr* field of function block ``INST_INVOKE`` and ``INST_CALL`` records.
811 The ``TYPE_BLOCK`` block (id 10) contains records which constitute a table of
815 constants, metadata, type symbol table entries, or other type operator records.