From f598db43e4868a95b02edd6ddf14b14cb38883f3 Mon Sep 17 00:00:00 2001 From: Nicholas Nethercote Date: Mon, 10 Jun 2002 10:24:05 +0000 Subject: [PATCH] A few minor improvements. git-svn-id: svn://svn.valgrind.org/valgrind/trunk@402 --- cachegrind/docs/manual.html | 50 ++++++++++++++++++++----------------- coregrind/docs/manual.html | 50 ++++++++++++++++++++----------------- docs/manual.html | 50 ++++++++++++++++++++----------------- memcheck/docs/manual.html | 50 ++++++++++++++++++++----------------- 4 files changed, 108 insertions(+), 92 deletions(-) diff --git a/cachegrind/docs/manual.html b/cachegrind/docs/manual.html index b5b1e2e963..9756d38088 100644 --- a/cachegrind/docs/manual.html +++ b/cachegrind/docs/manual.html @@ -1970,7 +1970,7 @@ very useful for improving the performance of your program.

Also, since one instruction cache read is performed per instruction executed, you can find out how many instructions are executed per line, which can be -useful for optimisation and test coverage.

+useful for traditional profiling and test coverage.

Please note that this is an experimental feature. Any feedback, bug-fixes, suggestions, etc, welcome. @@ -2009,7 +2009,7 @@ The two steps are: The steps are described in detail in the following sections.

-

7.3  Cache simulation specifics

+

7.2  Cache simulation specifics

Cachegrind uses a simulation for a machine with a split L1 cache and a unified L2 cache. This configuration is used for all (modern) x86-based machines we @@ -2074,7 +2074,7 @@ existing ones in vg_cachesim_I1.c, vg_cachesim_D1.c, interested to hear from anyone who does. -

7.4  Profiling programs

+

7.3  Profiling programs

Cache profiling is enabled by using the --cachesim=yes option to the valgrind shell script. Alternatively, it @@ -2121,7 +2121,7 @@ to the row's total).

Combined instruction and data figures for the L2 cache follow that.

-

7.5  Output file

+

7.4  Output file

As well as printing summary information, Cachegrind also writes line-by-line cache profiling information to a file named @@ -2142,32 +2142,31 @@ Things to note about the cachegrind.out file: -

7.6  Cachegrind options

+

7.5  Cachegrind options

Cachegrind accepts all the options that Valgrind does, although some of them (ones related to memory checking) don't do anything when cache profiling.

The interesting cache-simulation specific options are: -

  • --I1=<size>,<associativity>,<line_size>

    - --D1=<size>,<associativity>,<line_size>

    +

  • --I1=<size>,<associativity>,<line_size>
    + --D1=<size>,<associativity>,<line_size>
    --L2=<size>,<associativity>,<line_size>

    - [default: uses CPUID for cache configuration]

    + [default: uses CPUID for automagic cache configuration]

    Manually specifies the I1/D1/L2 cache configuration, where size and line_size are measured in bytes. The - three items must be comma-separated, but with no space, eg: + three items must be comma-separated, but with no spaces, eg:

    cachegrind --I1=65535,2,64
    - You can specify one, two or three of the caches. Any level not manually - specified will be simulated using the configuration found in the normal - way (via the CPUID instruction, or failing that, via defaults). + You can specify one, two or three of the I1/D1/L2 caches. Any level not + manually specified will be simulated using the configuration found in the + normal way (via the CPUID instruction, or failing that, via defaults). - - + -

    7.7  Annotating C/C++ programs

    +

    7.6  Annotating C/C++ programs

    Before using vg_annotate, it is worth widening your window to be at least 120-characters wide if possible, as the output @@ -2400,7 +2399,7 @@ Beware that vg_annotate can take some time to digest large auto-annotation can produce a lot of output if your program is large! -

    7.8  Annotating assembler programs

    +

    7.7  Annotating assembler programs

    Valgrind can annotate assembler programs too, or annotate the assembler generated for your C program. Sometimes this is useful for @@ -2418,7 +2417,7 @@ You can then profile and annotate source files in the same way as for C/C++ programs. -

    7.9  vg_annotate options

    +

    7.8  vg_annotate options

    -

    7.10  Warnings

    +

    7.9  Warnings

    There are a couple of situations in which vg_annotate issues warnings. -

    7.11  Things to watch out for

    +

    7.10  Things to watch out for

    Some odd things that can occur during annotation: