Lines Matching +full:document +full:- +full:file

5 --------------------------------------------------------
7 --------------------------------------------------------
9 --------------------------------------------------------
11 --------------------------------------------------------
17 This document describes the jitdump file format. The file is generated by Just-In-time compiler run…
21 The format of the file is binary. It is self-describing in terms of endianness and is portable acro…
27 …ires only sequential accesses, i.e., append only mode. The file starts with a fixed size file head…
31 Each entry in the file is timestamped. All timestamps must use the same clock source. The CLOCK_MON…
34 III/ Jitdump file header format
36 Each jitdump file starts with a fixed size header containing the following fields in order:
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
41 * uint32_t total_size: size in bytes of file header
45 * uint64_t timestamp : timestamp of when the file was created
49 …* bit 0: JITDUMP_FLAGS_ARCH_TIMESTAMP : set if the jitdump file is using an architecture-specific …
53 The file header is immediately followed by records. Each record starts with a fixed size header des…
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:
128 * uint32_t line : source file line number (starting at 1)
130 * char name[n] : source file name in ASCII, including null termination
132 … are saved in sequence but given that they have variable sizes due to the file name string, they c…
136 …EFORE the JIT_CODE_LOAD for the function. This facilitates greatly the parser for the jitdump file.
144 …d is used as a marker for the end of the jitted runtime. It can be replaced by the end of the file.
156 The record has the following fields following the fixed-size record header in order:
164 …follows the Linux Standard Base (LSB) specification as described in the document at https://refspe…
167 …s the LSB specification as described in the document at https://refspecs.linuxbase.org/LSB_3.0.0/L…