Home | History | Annotate | Download | only in docs

Lines Matching full:specify

10 <para>To use this tool, you must specify
191 interesting code section is executed. To exactly specify
195 <para>If you want to be able to see assembly code level annotation, specify
253 arbitrary string you can optionally specify to later be able to
279 <para>You can specify these options multiple times for different
298 <para>If you are running a multi-threaded application and specify the
619 These options specify when actions relating to event counts are to
675 These options specify when events are to be aggregated into event counts.
686 <para>Specify if you want Callgrind to start simulation and
713 <para>Specify whether event collection is enabled at beginning
801 These options specify how event counts should be attributed to execution
803 For example, they specify whether the recursion level or the
886 call chain A &gt; B &gt; C, and you specify function B to be
933 <para>Specify if you want to do full cache simulation. By default,
949 <para>Specify if you want to do branch prediction simulation.
974 <para>Specify whether write-back behavior should be simulated, allowing
976 The cache model of Cachegrind/Callgrind does not specify write-through
994 <para>Specify whether simulation of a hardware prefetcher should be
1009 <para>Specify whether cache line use should be collected. For every
1047 <para>Specify the size, associativity and line size of the level 1
1057 <para>Specify the size, associativity and line size of the level 1
1067 <para>Specify the size, associativity and line size of the last-level
1135 but allows to specify a string to be able to distinguish profile
1405 <para>Specify the startup directory of an active Callgrind run. On some