Mercurial > hg > CbC > CbC_llvm

comparison docs/XRayFDRFormat.rst @ 148:63bd29f05246

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
merged
author Shinji KONO <kono@ie.u-ryukyu.ac.jp>
date Wed, 14 Aug 2019 19:46:37 +0900
parents c2174574ed3a
children
comparison
equal deleted inserted replaced
146:3fc4d5c3e21e 148:63bd29f05246
13 13
14 When gathering XRay traces in Flight Data Recorder mode, each thread of an 14 When gathering XRay traces in Flight Data Recorder mode, each thread of an
15 application will claim buffers to fill with trace data, which at some point 15 application will claim buffers to fill with trace data, which at some point
16 is finalized and flushed. 16 is finalized and flushed.
17 17
18 A goal of the profiler is to minimize overhead, so the flushed data directly 18 A goal of the profiler is to minimize overhead, the flushed data directly
19 corresponds to the buffer. 19 corresponds to the buffer.
20 20
21 This document describes the format of a trace file. 21 This document describes the format of a trace file.
22 22
23 23
104 always preceded with a marker record which indicates how large it is. 104 always preceded with a marker record which indicates how large it is.
105 105
106 - ``Function Arguments``: The arguments to some functions are included in the 106 - ``Function Arguments``: The arguments to some functions are included in the
107 trace. These are either pointer addresses or primitives that are read and 107 trace. These are either pointer addresses or primitives that are read and
108 logged independently of their types in a high level language. To the tracer, 108 logged independently of their types in a high level language. To the tracer,
109 they are all simply numbers. Function Records that have attached arguments 109 they are all numbers. Function Records that have attached arguments will
110 will indicate their presence on the function entry record. We only support 110 indicate their presence on the function entry record. We only support logging
111 logging contiguous function argument sequences starting with argument zero, 111 contiguous function argument sequences starting with argument zero, which will
112 which will be the "this" pointer for member function invocations. For example, 112 be the "this" pointer for member function invocations. For example, we don't
113 we don't support logging the first and third argument. 113 support logging the first and third argument.
114 114
115 A reader of the memory format must maintain a state machine. The format makes no 115 A reader of the memory format must maintain a state machine. The format makes no
116 attempt to pad for alignment, and it is not seekable. 116 attempt to pad for alignment, and it is not seekable.
117 117
118 118