Lines Matching refs:record

29 …xed size header describing the type of record and its size. It is, itself, followed by the payload…
53 …ader is immediately followed by records. Each record starts with a fixed size header describing th…
55 The record header is specified in order as follows:
56 * uint32_t id        : a value identifying the record type (see below)
57 * uint32_t total_size: the size in bytes of the record including the header.
58 * uint64_t timestamp : a timestamp of when the record was created.
60 The following record types are defined:
61  * Value 0 : JIT_CODE_LOAD      : record describing a jitted function
62  * Value 1 : JIT_CODE_MOVE      : record describing an already jitted function which is moved
63  * Value 2 : JIT_CODE_DEBUG_INFO: record describing the debug information for a jitted function
64  * Value 3 : JIT_CODE_CLOSE     : record marking the end of the jit runtime (optional)
65  * Value 4 : JIT_CODE_UNWINDING_INFO: record describing a function unwinding information
67  The payload of the record must immediately follow the record header without padding.
69 V/ JIT_CODE_LOAD record
72   The record has the following fields following the fixed-size record header in order:
82   The record header total_size field is inclusive of all components:
83   * record header
87   * record specific variable data (e.g., array of data entries)
89 …d in case the code for a function is moved and avoids having to issue another JIT_CODE_LOAD record.
94 VI/ JIT_CODE_MOVE record
96   The record type is optional.
98   The record has the following fields following the fixed-size record header in order:
105 …* uint64_t code_index   : index referring to the JIT_CODE_LOAD code_index record of when the funct…
108 The MOVE record can be used in case an already jitted function is simply moved by the runtime insid…
110 …record cannot come before the JIT_CODE_LOAD record for the same function name. The function cannot…
115 VII/ JIT_DEBUG_INFO record
117 The record type is optional.
119 The record contains source lines debug information, i.e., a way to map a code address back to a sou…
121 The record has the following fields following the fixed-size record header in order:
139 VIII/ JIT_CODE_CLOSE record
142 The record type is optional.
144 The record is used as a marker for the end of the jitted runtime. It can be replaced by the end of …
146 The JIT_CODE_CLOSE record does not have any specific fields, the record header contains all the inf…
152 The record type is optional.
154 The record is used to describe the unwinding information for a jitted function.
156 The record has the following fields following the fixed-size record header in order:
158 uint64_t unwind_data_size   : the size in bytes of the unwinding data table at the end of the record
159 …ytes of the DWARF EH Frame Header at the start of the unwinding data table at the end of the record