Searched refs:cumulative (Results 1 – 14 of 14) sorted by relevance
5 cumulative a running sum of the number of seconds accounted
306 % cumulative self self total779 cumulative data in the file @file{gmon.sum}.936 % cumulative self self total970 seconds, as indicated by the @samp{cumulative seconds} field. Since1001 @item cumulative seconds1002 This is the cumulative total number of seconds the computer spent1452 % cumulative self self total1485 % cumulative self1678 Analyze the cumulative data using this command:2122 are cumulative.
148 % cumulative self self total597 cumulative data in the file `gmon.sum'.744 % cumulative self self total774 `cumulative seconds' field. Since each sample counted for 0.01798 `cumulative seconds'799 This is the cumulative total number of seconds the computer spent1233 % cumulative self self total1262 % cumulative self1444 6. Analyze the cumulative data using this command:1850 call counts are cumulative.
1967 struct load_progress_data *cumulative; member1990 totals = args->cumulative; in load_progress()2071 section_data->cumulative = args->progress_data; in load_section_callback()
211 /* Indicates the cumulative offset of the stack pointer accounting
217 /* Indicates the cumulative offset of the stack pointer accounting
465 The execution counts are cumulative. If the example program were
9188 parameters only when their cumulative size is less or equal to
1412 * The formula for the Pareto cumulative probability function is
3232 commands are cumulative in a given section, but users allowed in any given
6642 included in cumulative descriptor offset, resulting in incorrect values 13251 functions. This reduces the cumulative stack use during nested execution
11814 cirro-cumulative
46746 cumulative