Lines Matching full:inclusive
70 this builds up a picture of so called <emphasis>inclusive</emphasis>
74 <para>As an example, the inclusive cost of
79 objects, the inclusive cost of <function>main</function>
141 <para><option>--inclusive=yes</option>: Instead of using
143 inclusive cost.</para>
155 cost, gives the total inclusive cost of the function.</para>
399 analysis of your code harder. This is because inclusive costs
401 inclusive cost, i.e. self cost of a function plus inclusive cost
405 and skips visualization of any inclusive cost for calls inside
414 inclusive cost. In addition, KCachegrind loses its ability to show
415 interesting parts of the call graph, as it uses inclusive costs to
418 <para>Despite the meaningless of inclusive costs in cycles, the big
424 calls with very small measured inclusive cost would break these
430 recursion, it e.g. can print nonsense inclusive costs way above 100%.</para>
1036 not possible to provide meaningful inclusive costs. Therefore,
1037 inclusive cost of these counters should be ignored.
1266 <option><![CDATA[--inclusive=<yes|no> [default: no] ]]></option>
1350 combined with -e to show inclusive cost of active functions.</para>
1361 this option is combined with -b, inclusive cost for the functions of
