Lines Matching full:cost
36 the meaning of cost lines in the second part of the file: the value of
38 of event type names. Cost lines consist of subpositions followed by 64-bit
46 function name or "fl" for a file name. Cost lines are always related to
68 "Instructions", and "Flops". Thus, cost lines give the number of CPU cycles
72 to "line", which means that the first number of a cost line is always a line
75 <para>Thus, the first cost line specifies that in line 15 of source file
81 file <filename>file.f</filename>, taking 20 CPU cycles. If a cost line
86 <para>Note that regular cost lines always give self (also called exclusive)
87 cost of code at a given position. If you specify multiple cost lines for the
107 (Source position) (Inclusive cost of call)
116 The second line looks like a regular cost line with the difference
117 that inclusive cost spent inside of the function call has to be specified.</para>
158 is executed where also the other functions are called. Inclusive cost of
159 <function>main</function> is 820, which is the sum of self cost 20 and costs
215 the meaning of subsequent cost lines or associations, they can appear
217 define name compression mappings directly after the header, and before any cost
242 and each cost line has to include the address of some instruction. Addresses
246 motivates for subposition compression: instead of every cost line starting with
252 of the last cost line, and starts with a "+" to specify a positive difference,
286 <sect3 id="cl-format.overview.misc.summary" xreflabel="Cost Summary Information">
287 <title>Cost Summary Information</title>
289 <para>For the visualization to be able to show cost percentage, a sum of the
290 cost of the full run has to be known. Usually, it is assumed that this is the
291 sum of all cost lines in a file. But sometimes, this is not correct. Thus, you
292 can specify a "summary:" line in the header giving the full cost for the
301 <para>Event types for cost lines are specified in the "events:" line with an
446 block counter, for which the cost of this dump was collected.
453 <para>For cost lines, this defines the semantic of the first numbers.
456 the cost lines later in the file.</para>
471 <para>A list of short names of the event types logged in cost
474 in cost lines. Thus, the first event type is the second or third
475 number in a cost line, depending on the value of "positions".
481 <para>Optional. This header line specifies a summary cost, which should be
483 the cost lines may not represent all cost of the program run.</para>
489 looking like a header line). Must give the total of all cost lines,
500 <para>The regular body line is a cost line consisting of one or two
502 and an array of cost numbers. A position number either is a
505 below). The cost numbers get mapped to event types in the same order
530 <para>The ELF object where the cost of next cost lines happens.</para>
544 the cost of next cost lines. "fi="/"fe=" is used when the source
550 <para>The name of the function where the cost of next cost lines
556 <para>The ELF object of the target of the next call cost lines.</para>
562 next call cost lines.</para>
573 <para>The name of the target function of the next call cost
580 related to one position as regular cost lines. It starts with specific
588 After a "calls=" line there MUST be a cost line. This provides the source position
589 of the call and the cost spent in the called function in total.</para>
