Note that this dictates the order the functions appear. It is <b>not</b>
the order in which the columns appear; that is dictated by the "events
- shown" line (and can be changed with the <code>--sort</code> option).
+ shown" line (and can be changed with the <code>--show</code> option).
</li><p>
<li>Threshold: <code>vg_annotate</code> by default omits functions
</ul>
Then follows summary statistics for the whole program. These are similar
-to the summary provided when running <code>valgrind --cachesim=yes</code>.<p>
+to the summary provided when running <code>cachegrind</code>.<p>
Then follows function-by-function statistics. Each function is
identified by a <code>file_name:function_name</code> pair. If a column
Note that this dictates the order the functions appear. It is <b>not</b>
the order in which the columns appear; that is dictated by the "events
- shown" line (and can be changed with the <code>--sort</code> option).
+ shown" line (and can be changed with the <code>--show</code> option).
</li><p>
<li>Threshold: <code>vg_annotate</code> by default omits functions
</ul>
Then follows summary statistics for the whole program. These are similar
-to the summary provided when running <code>valgrind --cachesim=yes</code>.<p>
+to the summary provided when running <code>cachegrind</code>.<p>
Then follows function-by-function statistics. Each function is
identified by a <code>file_name:function_name</code> pair. If a column
Note that this dictates the order the functions appear. It is <b>not</b>
the order in which the columns appear; that is dictated by the "events
- shown" line (and can be changed with the <code>--sort</code> option).
+ shown" line (and can be changed with the <code>--show</code> option).
</li><p>
<li>Threshold: <code>vg_annotate</code> by default omits functions
</ul>
Then follows summary statistics for the whole program. These are similar
-to the summary provided when running <code>valgrind --cachesim=yes</code>.<p>
+to the summary provided when running <code>cachegrind</code>.<p>
Then follows function-by-function statistics. Each function is
identified by a <code>file_name:function_name</code> pair. If a column
Note that this dictates the order the functions appear. It is <b>not</b>
the order in which the columns appear; that is dictated by the "events
- shown" line (and can be changed with the <code>--sort</code> option).
+ shown" line (and can be changed with the <code>--show</code> option).
</li><p>
<li>Threshold: <code>vg_annotate</code> by default omits functions
</ul>
Then follows summary statistics for the whole program. These are similar
-to the summary provided when running <code>valgrind --cachesim=yes</code>.<p>
+to the summary provided when running <code>cachegrind</code>.<p>
Then follows function-by-function statistics. Each function is
identified by a <code>file_name:function_name</code> pair. If a column