Lines Matching refs:gcov

28 @setfilename gcov
33 @chapter @command{gcov}---a Test Coverage Program
35 @command{gcov} is a tool you can use in conjunction with GCC to
39 * Gcov Intro::                  Introduction to gcov.
40 * Invoking Gcov::               How to use gcov.
41 * Gcov and Optimization::       Using gcov with GCC optimization.
42 * Gcov Data Files::             The files used by gcov.
47 @section Introduction to @command{gcov}
50 @command{gcov} is a test coverage program.  Use it in concert with GCC
53 @command{gcov} as a profiling tool to help discover where your
55 @command{gcov} along with the other profiling tool, @command{gprof}, to
60 profiler such as @command{gcov} or @command{gprof}, you can find out some
76 @command{gcov} helps you determine where to work on optimization.
87 @command{gcov} because the optimization, by combining some lines of code
90 time.  Likewise, because @command{gcov} accumulates statistics by line (at
98 @command{gcov} creates a logfile called @file{@var{sourcefile}.gcov} which
103 @command{gcov}.
105 @command{gcov} works only on code compiled with GCC@.  It is not
111 @section Invoking @command{gcov}
114 gcov @r{[}@var{options}@r{]} @var{files}
117 @command{gcov} accepts the following options:
121 gcov [@option{-v}|@option{--version}] [@option{-h}|@option{--help}]
153 Write individual execution counts for every basic block.  Normally gcov
180 Display help about using @command{gcov} (on the standard output), and
185 Output gcov file in an easy-to-parse JSON intermediate format
188 and the files have @file{.gcov.json.gz} extension.
357 @file{a.c}, then running @command{gcov} on the file @file{a.c} will
358 produce an output file called @file{a.c##x.h.gcov} instead of
359 @file{x.h.gcov}.  This can be useful if @file{x.h} is included in
371 Do not create the @command{gcov} output file.
376 Specify either the directory containing the gcov data files, or the
386 @file{.gcov} files.  Without this option, just the filename component is
425 Display the @command{gcov} version number (on the standard output),
435 gcov uses the full pathname of the source files to create
438 @file{@var{source-file}##@var{md5}.gcov},
446 @command{gcov} should be run with the current directory the same as that
448 the source files.  @command{gcov} produces files called
449 @file{@var{mangledname}.gcov} in the current directory.  These contain
451 One @file{.gcov} file is produced for each source (or header) file
458 If you invoke @command{gcov} with multiple input files, the
462 The @file{.gcov} files contain the @samp{:} separated fields along with
486 allow gcov to properly show their @var{execution_count}.
496 @command{gcov} development progresses --- do not rely on them remaining
513 When using @command{gcov}, you must first compile your program
516 gcov (basically a flow graph of the program) and also includes
518 information needed by gcov.  These additional files are placed in the
525 Running @command{gcov} with your program's source file names as arguments
528 is what you see when you use the basic @command{gcov} facility:
533 $ gcov tmp.cpp -m
536 Creating 'tmp.cpp.gcov'
539 The file @file{tmp.cpp.gcov} contains output from @command{gcov}.
826 @section Using @command{gcov} with GCC Optimization
828 If you plan to use @command{gcov} to help optimize your code, you must
846 there is no way for @command{gcov} to calculate separate execution counts
848 the @command{gcov} output looks like this if you compiled the program with
908 @section Brief Description of @command{gcov} Data Files
910 @command{gcov} uses two files for profiling.  The names of these files
932 by @command{gcov} tool via @option{--json-format} option.
971 use the @command{gcov} tool.