GCOV-TOOL(1)
β¨ NAME β¨
gcov-tool β the offline gcda profile processing tool π
okay so real quick before we dive in: this is the gcov-tool page, it lives in the GNU manual, section 1, and it's about wrangling gcc's profile files without ever touching the live runtime. bestie, it's giving "spreadsheet girlboss but for counters". let's go π¦
πΈ SYNOPSIS πΈ
gcov-tool [-v|--version] [-h|--help]
gcov-tool merge [merge-options] directory1 directory2
[-o|--output directory]
[-v|--verbose]
[-w|--weight w1,w2]
gcov-tool merge-stream [merge-stream-options] [file]
[-v|--verbose]
[-w|--weight w1,w2]
gcov-tool rewrite [rewrite-options] directory
[-n|--normalize long_long_value]
[-o|--output directory]
[-s|--scale float_or_simple-frac_value]
[-v|--verbose]
gcov-tool overlap [overlap-options] directory1 directory2
[-f|--function]
[-F|--fullname]
[-h|--hotonly]
[-o|--object]
[-t|--hot_threshold] float
[-v|--verbose]
like, four whole modes and a help/version moment. pick your fighter π
π DESCRIPTION π
So gcov-tool is an offline tool that processes gcc's gcda profile files. no cap. it does not need the program to be running, it just vibes with the files on disk.
Right now gcov-tool supports these functionalities:
- merge two sets of profiles with weights β¨
- read a stream of profiles with associated filenames and merge it with a set of profiles with weights π
- read one set of profile and rewrite profile contents. One can scale or normalize the count values π₯
And here are some use cases, because i know you're gonna ask:
- Collect the profiles for different set of inputs, and use this tool to merge them. One can specify the weight to factor in the relative importance of each input π
- Collect profiles from target systems without a filesystem (freestanding environments). Merge the collected profiles with associated profiles present on the host system. One can specify the weight to factor in the relative importance of each input πΈ
- Rewrite the profile after removing a subset of the gcda files, while maintaining the consistency of the summary and the histogram π
- It can also be used to debug or libgcov code as the tools shares the majority code as the runtime library π§
okay heads up, this is the important bit: for the merging operation, this profile generated offline may contain slight different values from the online merged profile. like, it's expected, don't panic. here's the list of typical differences:
- histogram difference: This offline tool recomputes the histogram after merging the counters. The resulting histogram, therefore, is precise. The online merging does not have this capability β the histogram is merged from two histograms and the result is an approximation. (we ate that one, honestly πβ¨)
- summary checksum difference: Summary checksum uses a CRC32 operation. The value depends on the link list order of gcov-info objects. This order is different in
gcov-toolfrom that in the online merge. It's expected to have different summary checksums. It does not really matter as the compiler does not use this checksum anywhere. π so like, breathe. - value profile counter values difference: Some counter values for value profile are runtime dependent, like heap addresses. It's normal to see some difference in these kind of counters.
π OPTIONS π
the basics
-h,--helpβ Display help about usinggcov-tool(on the standard output), and exit without doing any further processing. the "wait what does this do again" button π«Ά-v,--versionβ Display thegcov-toolversion number (on the standard output), and exit without doing any further processing. slay, now you know what you're running.
merge π
Merge two profile directories.
-o directory,--output directoryβ Set the output profile directory. Default output directory name ismerged_profile.-v,--verboseβ Set the verbose mode.-w w1,w2,--weight w1,w2β Set the merge weights of thedirectory1anddirectory2, respectively. The default weights are1for both.
merge-stream π¦
Collect profiles with associated filenames from a gcfn and gcda data stream. Read the stream from the file specified by file or from stdin. Merge the profiles with associated profiles in the host filesystem. Apply the optional weights while merging profiles.
For the generation of a gcfn and gcda data stream on the target system, please have a look at the "__gcov_filename_to_gcfn()" and "__gcov_info_to_gcda()" functions declared in "#include <gcov.h>". π
-v,--verboseβ Set the verbose mode.-w w1,w2,--weight w1,w2β Set the merge weights of the profiles from the gcfn and gcda data stream and the associated profiles in the host filesystem, respectively. The default weights are1for both.
rewrite πΈ
Read the specified profile directory and rewrite to a new directory.
-n long_long_value,--normalize <long_long_value>β Normalize the profile. The specified value is the max counter value in the new profile.-o directory,--output directoryβ Set the output profile directory. Default output name isrewrite_profile.-s float_or_simple-frac_value,--scale float_or_simple-frac_valueβ Scale the profile counters. The specified value can be in floating point value, or simple fraction value form, such1,2,2/3, and5/3.-v,--verboseβ Set the verbose mode.
overlap π
Compute the overlap score between the two specified profile directories. The overlap score is computed based on the arc profiles. It is defined as the sum of min (p1_counter[i] / p1_sum_all, p2_counter[i] / p2_sum_all), for all arc counter i, where p1_counter[i] and p2_counter[i] are two matched counters and p1_sum_all and p2_sum_all are the sum of counter values in profile 1 and profile 2, respectively. it's like a compatibility score but for profiles, highkey romantic π
-f,--functionβ Print function level overlap score.-F,--fullnameβ Print full gcda filename.-h,--hotonlyβ Only print info for hot objects/functions. π₯-o,--objectβ Print object level overlap score.-t float,--hot_threshold <float>β Set the threshold for hot counter value.-v,--verboseβ Set the verbose mode.
lowkey watch out β inoverlap,-his--hotonly, not help. the help one is--help. don't get got π
π SEE ALSO π
gpl(7), gfdl(7), fsf-funding(7), gcc(1), gcov(1) and the Info entry for gcc.
go read those too, they're the extended universe bestie πβ¨
π COPYRIGHT π
Copyright (c) 2014-2024 Free Software Foundation, Inc.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with the Invariant Sections being "GNU General Public License" and "Funding Free Software", the Front-Cover texts being (a) (see below), and with the Back-Cover Texts being (b) (see below). A copy of the license is included in the gfdl(7) man page.
(a) The FSF's Front-Cover Text is:
A GNU Manual
(b) The FSF's Back-Cover Text is:
You have freedom to copy and modify this GNU Manual, like GNU
software. Copies published by the Free Software Foundation raise
funds for GNU development.
and that's the whole page, bestie π
this was gcc-14.4.0, dated 2026-06-26, and it's the GCOV-TOOL(1) page, GNU edition. go merge some profiles, you're gonna eat. periodt πβ¨π¦
π¦ where this page comes from
- ubuntu stonking: gcc-14-loongarch64-linux-gnu 14.4.0-2ubuntu1cross2
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms