Lines Matching full:profile
27 <para>The profile data is written out to a file at program
34 <para>This command reads in the profile data, and prints a
52 or dumping of profile data.</para>
60 <para>Cachegrind collects flat profile data: event counts (data reads,
110 <para>To start a profile run for a program, execute:
121 <para>After program termination, a profile data file named
129 <para>To generate a function-by-function summary from the profile
183 <para>If the program section you want to profile is somewhere in the
197 profile data at instruction granularity. Note that the resulting profile
219 profile information for different parts of a single program run.</para>
221 <para>Profile data files have names of the form
233 <para>There are different ways to generate multiple profile dumps
235 all methods trigger the same action, which is "dump all profile
251 request the dumping of profile information of the supervised
254 distinguish profile dumps. The control program will not terminate
260 for browsing of profile information, you can use the toolbar
290 at the position in your code where you want a profile dump to happen. Use
292 zero profile counters.
301 profile dump. Thus, the last two methods will only generate one dump
423 the profile result will see a cycle. Neglecting uninteresting
434 the profile data do not have to exactly match the symbols found in the
441 with possible out-of-memory conditions, and big profile data files.</para>
443 <para>A further possibility to avoid cycles in Callgrind's profile data
452 if you profile with <option><xref linkend="opt.skip-plt"/>=no</option>.
461 give you much bigger profile data files. In the profile data, you will see
475 the size of profile data files.</para>
483 data that has been gathered for the parent. To start with empty profile
526 These options influence the name and format of the profile data files.
537 <para>Write the profile data to
580 <para>This option influences the output format of the profile data.
593 <para>This option influences the output format of the profile data.
605 <para>When enabled, when multiple profile data parts are to be
631 <para>Dump profile data every <option>count</option> basic blocks.
714 of the profile run.</para>
720 want to profile, and dump the event counters to a file after
726 profile.</para>
730 profile is called many times. Option 1, i.e. creating a lot of
816 <para>This option specifies whether profile data should be generated
1087 profile data. </para>
1091 <para><varname>zero</varname> requests to zero the profile data
1123 <para>Force generation of a profile dump at specified position
1135 but allows to specify a string to be able to distinguish profile
1145 <para>Reset the profile counters for the current thread to zero.</para>
1155 with regard to profile counters. See also options
1370 <para>Request the dumping of profile information. Optionally, a
