Lines Matching +full:self +full:- +full:describing
5 --------------------------------------------------------
7 --------------------------------------------------------
9 --------------------------------------------------------
11 --------------------------------------------------------
17 …s the jitdump file format. The file is generated by Just-In-time compiler runtimes to save meta-da…
21 The format of the file is binary. It is self-describing in terms of endianness and is portable acro…
27 … i.e., append only mode. The file starts with a fixed size file header describing the version of t…
29 The header is followed by a series of records, each starting with a fixed size header describing th…
39 * uint32_t magic : a magic number tagging the file type. The value is 4-byte long and represent…
40 * uint32_t version : a 4-byte value representing the format version. It is currently set to 1
49 …* bit 0: JITDUMP_FLAGS_ARCH_TIMESTAMP : set if the jitdump file is using an architecture-specific …
53 …ately followed by records. Each record starts with a fixed size header describing the record that …
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
65 * Value 4 : JIT_CODE_UNWINDING_INFO: record describing a function unwinding information
72 The record has the following fields following the fixed-size record header in order:
84 * fixed-sized fields
89 …dentify each jitted function. The index can be a monotonically increasing 64-bit value. Each time …
98 The record has the following fields following the fixed-size record header in order:
121 The record has the following fields following the fixed-size record header in order:
156 The record has the following fields following the fixed-size record header in order:
167 …escribed in the document at https://refspecs.linuxbase.org/LSB_3.0.0/LSB-PDA/LSB-PDA/ehframechpt.h…