Lines Matching refs:is
17 This document describes the jitdump file format. The file is generated by Just-In-time compiler run…
19 The format is not specific to any particular programming language. It can be extended as need be.
21 The format of the file is binary. It is self-describing in terms of endianness and is portable acro…
29 The header is followed by a series of records, each starting with a fixed size header describing th…
31 Each entry in the file is timestamped. All timestamps must use the same clock source. The CLOCK_MON…
39 …mber tagging the file type. The value is 4-byte long and represents the string "JiTD" in ASCII for…
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 The file header is immediately followed by records. Each record starts with a fixed size header des…
55 The record header is specified in order as follows:
62 * Value 1 : JIT_CODE_MOVE : record describing an already jitted function which is moved
82 The record header total_size field is inclusive of all components:
89 …is used to uniquely identify each jitted function. The index can be a monotonically increasing 64-…
96 The record type is optional.
108 The MOVE record can be used in case an already jitted function is simply moved by the runtime insid…
117 The record type is optional.
122 * uint64_t code_addr: address of function for which the debug information is generated
126 The debug_entry describes the source line information. It is defined as follows in order:
127 * uint64_t code_addr: address of function for which the debug information is generated
129 * uint32_t discrim : column discriminator, 0 is default
133 They need to be walked sequentially. The next debug_entry is found at sizeof(debug_entry) + strlen(…
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 …
152 The record type is optional.
154 The record is used to describe the unwinding information for a jitted function.
170 … is generally either the same as unwind_data_size (if the unwinding data was mapped in memory by t…