GCOV(1)
👑 gcov(1) — GNU’s own coverage queen 👑
ok so this is the manual page for <pink>gcov</pink>, and yes it’s a GNU thing, and yes it is about to become your whole personality for the next however-long. sit down bestie, we’re doing coverage. 💅
✨ NAME ✨
gcov — coverage testing tool 🎀
🦋 SYNOPSIS 🦋
gcov [-v|--version] [-h|--help]
[-a|--all-blocks]
[-b|--branch-probabilities]
[-c|--branch-counts]
[-d|--display-progress]
[-f|--function-summaries]
[-j|--json-format]
[-H|--human-readable]
[-k|--use-colors]
[-l|--long-file-names]
[-m|--demangled-names]
[-n|--no-output]
[-o|--object-directory directory|file]
[-p|--preserve-paths]
[-q|--use-hotness-colors]
[-r|--relative-only]
[-s|--source-prefix directory]
[-t|--stdout]
[-u|--unconditional-branches]
[-x|--hash-filenames]
filesthat’s the whole vibe right there. files at the end, everything else is optional flags. no cap.
💖 DESCRIPTION 💖
okay so <pink>gcov</pink> is a test coverage program. like, its whole job is finding out which parts of your code actually ran and which parts are just sitting there collecting dust. 🫧
you use it in concert with GCC to analyze your programs, so you can make more efficient, faster running code, and so you can discover the untested parts of your program. you can also use <pink>gcov</pink> as a profiling tool — the kind that tells you where your optimization efforts will best affect your code. and you can run it alongside the other profiling tool, <purple>gprof</purple>, to assess which parts of your code are eating the greatest amount of computing time. teamwork!! 🤝
profiling tools help you analyze your code’s performance. with a profiler like <pink>gcov</pink> or <purple>gprof</purple>, you can find out some basic performance statistics, like:
- how often each line of code executes 👀
- what lines of code are actually executed 💀 (some of them are NOT. the audacity.)
- how much computing time each section of code uses ⏱️
once you know these things about how your code works when compiled, you can look at each module to see which modules should be optimized. <pink>gcov</pink> helps you determine where to work on optimization. she’s basically your little optimization compass. 🧭
software developers also use coverage testing in concert with testsuites, to make sure software is actually good enough for a release. testsuites can verify that a program works as expected; a coverage program tests to see how much of the program is exercised by the testsuite. then developers can determine what kinds of test cases need to be added to the testsuites, so they get both better testing and a better final product. it’s giving ✨personal growth✨.
okay this next part is IMPORTANT bestie so read it twice:
you should compile your code without optimization if you plan to use <pink>gcov</pink>, because the optimization — by combining some lines of code into one function — may not give you as much information as you need to look for 'hot spots' where the code is using a great deal of computer time. 🔥
likewise, because <pink>gcov</pink> accumulates statistics by line (at the lowest resolution), it works best with a programming style that places only one statement on each line. if you use complicated macros that expand to loops or to other control structures, the statistics are less helpful — they only report on the line where the macro call appears. 😭 if your complex macros behave like functions, you can replace them with inline functions to solve this problem. slay, problem solved. 💅
<pink>gcov</pink> creates a logfile called sourcefile.gcov which indicates how many times each line of a source file sourcefile.c has executed. you can use these logfiles along with <purple>gprof</purple> to aid in fine-tuning the performance of your programs. <purple>gprof</purple> gives timing information you can use along with the information you get from <pink>gcov</pink>. iconic duo fr fr. 🫶
🚨 real talk: <pink>gcov</pink> works only on code compiled with GCC. it is not compatible with any other profiling or test coverage mechanism. she’s exclusive. she has a type. it’s GCC. 💅
🌈 OPTIONS 🌈
-a,--all-blocks— write individual execution counts for every basic block. normally<pink>gcov</pink>only outputs execution counts for the main blocks of a line. with this option you can determine if blocks within a single line are not being executed. deep dive energy 🔍-b,--branch-probabilities— write branch frequencies to the output file, and write branch summary info to the standard output. this option lets you see how often each branch in your program was taken. unconditional branches will not be shown, unless the-uoption is given. (she’s picky like that 💅)-c,--branch-counts— write branch frequencies as the number of branches taken, rather than the percentage of branches taken. numbers girlies rise 🧮-d,--display-progress— display the progress on the standard output. so you can watch her work. ✨-f,--function-summaries— output summaries for each function, in addition to the file level summary. every single one. no function left behind 🫶-h,--help— display help about using<pink>gcov</pink>(on the standard output), and exit without doing any further processing. a polite little exit. 🎀-j,--json-format— output the<pink>gcov</pink>file in an easy-to-parse JSON intermediate format which does not require source code for generation. the JSON file is compressed with gzip compression algorithm and the files have.gcov.json.gzextension. 🗜️
structure of the JSON is following:
{
"current_working_directory": "foo/bar",
"data_file": "a.out",
"format_version": "1",
"gcc_version": "11.1.1 20210510"
"files": ["$file"]
}fields of the root element have following semantics:
current_working_directory: working directory where a compilation unit was compileddata_file: name of the data file (GCDA)format_version: semantic version of the formatgcc_version: version of the GCC compiler
each file has the following form:
{
"file": "a.c",
"functions": ["$function"],
"lines": ["$line"]
}fields of the file element have following semantics:
file_name: name of the source file
each function has the following form:
{
"blocks": 2,
"blocks_executed": 2,
"demangled_name": "foo",
"end_column": 1,
"end_line": 4,
"execution_count": 1,
"name": "foo",
"start_column": 5,
"start_line": 1
}fields of the function element have following semantics:
blocks: number of blocks that are in the functionblocks_executed: number of executed blocks of the functiondemangled_name: demangled name of the functionend_column: column in the source file where the function endsend_line: line in the source file where the function endsexecution_count: number of executions of the functionname: name of the functionstart_column: column in the source file where the function beginsstart_line: line in the source file where the function begins
note that line numbers and column numbers number from1. in the current implementation,start_lineandstart_columndo not include any template parameters and the leading return type but that this is likely to be fixed in the future. (future update pending, bestie ⏳)
each line has the following form:
{
"branches": ["$branch"],
"count": 2,
"line_number": 15,
"unexecuted_block": false,
"function_name": "foo",
}branches are present only with -b option. fields of the line element have following semantics:
count: number of executions of the lineline_number: line numberunexecuted_block: flag whether the line contains an unexecuted block (not all statements on the line are executed)function_name: a name of a function this line belongs to (for a line with an inlined statements can be not set)
each branch has the following form:
{
"count": 11,
"fallthrough": true,
"throw": false
}fields of the branch element have following semantics:
count: number of executions of the branchfallthrough:truewhen the branch is a fall through branchthrow:truewhen the branch is an exceptional branch
-H,--human-readable— write counts in human readable format (like24.6k). because24600is not the moment, but24.6kis 💅-k,--use-colors— use colors for lines of code that have zero coverage. we use red color for non-exceptional lines and cyan for exceptional. same colors are used for basic blocks with the-aoption. aesthetic AND informative 🌈-l,--long-file-names— create long file names for included source files. for example, if the header filex.hcontains code, and was included in the filea.c, then running<pink>gcov</pink>on the filea.cwill produce an output file calleda.c##x.h.gcovinstead ofx.h.gcov. this can be useful ifx.his included in multiple source files and you want to see the individual contributions. if you use the-poption, both the including and included file names will be complete path names. 🧵-m,--demangled-names— display demangled function names in output. the default is to show mangled function names. (mangled names are giving_ZN3fooEv💀, demangled is givingfoo🫶)-n,--no-output— do not create the<pink>gcov</pink>output file. look but don’t touch energy 🙈-odirectory|file,--object-directorydirectory,--object-filefile — specify either the directory containing the<pink>gcov</pink>data files, or the object path name. the.gcno, and.gcdadata files are searched for using this option. if a directory is specified, the data files are in that directory and named after the input file name, without its extension. if a file is specified here, the data files are named after that file, without its extension. 📁-p,--preserve-paths— preserve complete path information in the names of generated.gcovfiles. without this option, just the filename component is used. with this option, all directories are used, with/characters translated to#characters,.directory components removed and unremoveable..components renamed to^. this is useful if sourcefiles are in several different directories. (the path gettin a whole makeover 💅)-q,--use-hotness-colors— emit perf-like colored output for hot lines. legend of the color scale is printed at the very beginning of the output file. 🔥 hot lines stay hot 🔥-r,--relative-only— only output information about source files with a relative pathname (after source prefix elision). absolute paths are usually system header files and coverage of any inline functions therein is normally uninteresting. we don’t care about them, respectfully 💀-sdirectory,--source-prefixdirectory — bestie, this one is a prefix for source file names that you want stripped off when gcov makes its output coverage files. It's literally made for when you build in a whole separate directory and you do not want that long source path showing up in the output filenames. Heads up though: this prefix detection happens before gcov figures out whether the source file is absolute. So order matters, okay? 💅-t,--stdout— output goes to standard output instead of into output files. Simple as that. ✨-u,--unconditional-branches— when branch probabilities are being printed, this says include the unconditional branches too. Normally unconditional branches are just not interesting, so they get left out. But if you want the full tea, here you go. 🍵-v,--version— shows thegcovversion number on standard output, then dips out immediately. No further processing, periodt. 👑-w,--verbose— prints verbose info related to basic blocks and arcs. That's it. 🧚-x,--hash-filenames— okay so when you use--preserve-paths,gcovuses the full pathname of the source files to build an output filename. That can give you long filenames that straight up overflow filesystem limits. This option instead makes names of the formsource-file##md5.gcov, where thesource-filepart is just the final filename part, and themd5part is calculated from the full mangled name that would've been used otherwise. It's an alternative to--preserve-pathson systems that have a filesystem limit. 🌈
gcov should be run with the current directory being the same as when you invoked the compiler. Otherwise it will not be able to locate the source files. No cap. 😭
gcov produces files called mangledname.gcov in the current directory. These contain the coverage information of the source file they correspond to. One .gcov file is produced for each source (or header) file containing code that was compiled to produce the data files. The mangledname part of the output file name is usually just the source file name, but it can be something more complicated if the -l or -p options are given. Refer to those options for details. 💖
If you invoke gcov with multiple input files, the contributions from each input file are summed. Typically you'd invoke it with the same list of files as the final link of your executable. Slay. ✨
The .gcov files contain : separated fields along with program source code. The format is:
<execution_count>:<line_number>:<source line text>Additional block information may succeed each line, when requested by command line option. The execution_count is - for lines containing no code. Unexecuted lines are marked ##### or =====, depending on whether they are reachable by non-exceptional paths or only exceptional paths such as C++ exception handlers, respectively. Given the -a option, unexecuted blocks are marked $$$$$ or %%%%%, depending on whether a basic block is reachable via non-exceptional or exceptional paths. Executed basic blocks having a statement with zero execution_count end with * character and are colored with magenta color with the -k option. This functionality is not supported in Ada. 💀
Note that GCC can completely remove the bodies of functions that are not needed — for instance if they are inlined everywhere. Such functions are marked with-, which can be confusing. Use the-fkeep-inline-functionsand-fkeep-static-functionsoptions to retain these functions and allowgcovto properly show theirexecution_count. 🙈
Some lines of information at the start have line_number of zero. These preamble lines are of the form:
-:0:<tag>:<value>The ordering and number of these preamble lines will be augmented as gcov development progresses — do not rely on them remaining unchanged. Use tag to locate a particular preamble line. 🎀
The additional block information is of the form:
<tag> <information>The information is human readable, but designed to be simple enough for machine parsing too. 🦋
When printing percentages, 0% and 100% are only printed when the values are exactly 0% and 100% respectively. Other values which would conventionally be rounded to 0% or 100% are instead printed as the nearest non-boundary value. 🌸
When using gcov, you must first compile your program with a special GCC option --coverage. This tells the compiler to generate additional information needed by gcov (basically a flow graph of the program) and also includes additional code in the object files for generating the extra profiling information needed by gcov. These additional files are placed in the directory where the object file is located. 🔥
Running the program will cause profile output to be generated. For each source file compiled with -fprofile-arcs, an accompanying .gcda file will be placed in the object file directory. 👑
Running gcov with your program's source file names as arguments will now produce a listing of the code along with frequency of execution for each line. For example, if your program is called tmp.cpp, this is what you see when you use the basic gcov facility:
$ g++ --coverage tmp.cpp -c
$ g++ --coverage tmp.o
$ a.out
$ gcov tmp.cpp -m
File 'tmp.cpp'
Lines executed:92.86% of 14
Creating 'tmp.cpp.gcov'The file tmp.cpp.gcov contains output from gcov. Here is a sample:
-: 0:Source:tmp.cpp
-: 0:Working directory:/home/gcc/testcase
-: 0:Graph:tmp.gcno
-: 0:Data:tmp.gcda
-: 0:Runs:1
-: 0:Programs:1
-: 1:#include <stdio.h>
-: 2:
-: 3:template<class T>
-: 4:class Foo
-: 5:{
-: 6: public:
1*: 7: Foo(): b (1000) {}
------------------
Foo<char>::Foo():
#####: 7: Foo(): b (1000) {}
------------------
Foo<int>::Foo():
1: 7: Foo(): b (1000) {}
------------------
2*: 8: void inc () { b++; }
------------------
Foo<char>::inc():
#####: 8: void inc () { b++; }
------------------
Foo<int>::inc():
2: 8: void inc () { b++; }
------------------
-: 9:
-: 10: private:
-: 11: int b;
-: 12:};
-: 13:
-: 14:template class Foo<int>;
-: 15:template class Foo<char>;
-: 16:
-: 17:int
1: 18:main (void)
-: 19:{
-: 20: int i, total;
1: 21: Foo<int> counter;
-: 22:
1: 23: counter.inc();
1: 24: counter.inc();
1: 25: total = 0;
-: 26:
11: 27: for (i = 0; i < 10; i++)
10: 28: total += i;
-: 29:
1*: 30: int v = total > 100 ? 1 : 2;
-: 31:
1: 32: if (total != 45)
#####: 33: printf ("Failure\n");
-: 34: else
1: 35: printf ("Success\n");
1: 36: return 0;
-: 37:}Note that line 7 is shown in the report multiple times. First occurrence presents total number of execution of the line and the next two belong to instances of class Foo constructors. As you can also see, line 30 contains some unexecuted basic blocks and thus execution count has asterisk symbol. 😭
When you use the -a option, you will get individual block counts, and the output looks like this:
-: 0:Source:tmp.cpp
-: 0:Working directory:/home/gcc/testcase
-: 0:Graph:tmp.gcno
-: 0:Data:tmp.gcda
-: 0:Runs:1
-: 0:Programs:1
-: 1:#include <stdio.h>
-: 2:
-: 3:template<class T>
-: 4:class Foo
-: 5:{
-: 6: public:
1*: 7: Foo(): b (1000) {}
------------------
Foo<char>::Foo():
#####: 7: Foo(): b (1000) {}
------------------
Foo<int>::Foo():
1: 7: Foo(): b (1000) {}
------------------
2*: 8: void inc () { b++; }
------------------
Foo<char>::inc():
#####: 8: void inc () { b++; }
------------------
Foo<int>::inc():
2: 8: void inc () { b++; }
------------------
-: 9:
-: 10: private:
-: 11: int b;
-: 12:};
-: 13:
-: 14:template class Foo<int>;
-: 15:template class Foo<char>;
-: 16:
-: 17:int
1: 18:main (void)
-: 19:{
-: 20: int i, total;
1: 21: Foo<int> counter;
1: 21-block 0
-: 22:
1: 23: counter.inc();
1: 23-block 0
1: 24: counter.inc();
1: 24-block 0
1: 25: total = 0;
-: 26:
11: 27: for (i = 0; i < 10; i++)
1: 27-block 0
11: 27-block 1
10: 28: total += i;
10: 28-block 0
-: 29:
1*: 30: int v = total > 100 ? 1 : 2;
1: 30-block 0
%%%%%: 30-block 1
1: 30-block 2
-: 31:
1: 32: if (total != 45)
1: 32-block 0
#####: 33: printf ("Failure\n");
%%%%%: 33-block 0
-: 34: else
1: 35: printf ("Success\n");
1: 35-block 0
1: 36: return 0;
1: 36-block 0
-: 37:}okay so in this mode, every basic block gets exactly one line of screentime — and it's the last line of the block, bestie. 💅 That's the whole vibe.
Which means a multi-line block only contributes to the execution count of that last line, and the other lines won't be shown as containing code — unless previous blocks end on those lines. The total execution count of a line gets shown, and then the lines after it show the execution counts for the individual blocks that end on that line. And after each block? You get that block's branch and call counts, if you passed the -b option. ✨
Also, because of the way GCC instruments calls, you can get a call count hanging out after a line that has no individual blocks at all. And like — as you can see, line 33 contains a basic block that was not executed. 💀 iconic behaviour, honestly.
When you use the -b option, your output looks like this:
-: 0:Source:tmp.cpp
-: 0:Working directory:/home/gcc/testcase
-: 0:Graph:tmp.gcno
-: 0:Data:tmp.gcda
-: 0:Runs:1
-: 0:Programs:1
-: 1:#include <stdio.h>
-: 2:
-: 3:template<class T>
-: 4:class Foo
-: 5:{
-: 6: public:
1*: 7: Foo(): b (1000) {}
------------------
Foo<char>::Foo():
function Foo<char>::Foo() called 0 returned 0% blocks executed 0%
#####: 7: Foo(): b (1000) {}
------------------
Foo<int>::Foo():
function Foo<int>::Foo() called 1 returned 100% blocks executed 100%
1: 7: Foo(): b (1000) {}
------------------
2*: 8: void inc () { b++; }
------------------
Foo<char>::inc():
function Foo<char>::inc() called 0 returned 0% blocks executed 0%
#####: 8: void inc () { b++; }
------------------
Foo<int>::inc():
function Foo<int>::inc() called 2 returned 100% blocks executed 100%
2: 8: void inc () { b++; }
------------------
-: 9:
-: 10: private:
-: 11: int b;
-: 12:};
-: 13:
-: 14:template class Foo<int>;
-: 15:template class Foo<char>;
-: 16:
-: 17:int
function main called 1 returned 100% blocks executed 81%
1: 18:main (void)
-: 19:{
-: 20: int i, total;
1: 21: Foo<int> counter;
call 0 returned 100%
branch 1 taken 100% (fallthrough)
branch 2 taken 0% (throw)
-: 22:
1: 23: counter.inc();
call 0 returned 100%
branch 1 taken 100% (fallthrough)
branch 2 taken 0% (throw)
1: 24: counter.inc();
call 0 returned 100%
branch 1 taken 100% (fallthrough)
branch 2 taken 0% (throw)
1: 25: total = 0;
-: 26:
11: 27: for (i = 0; i < 10; i++)
branch 0 taken 91% (fallthrough)
branch 1 taken 9%
10: 28: total += i;
-: 29:
1*: 30: int v = total > 100 ? 1 : 2;
branch 0 taken 0% (fallthrough)
branch 1 taken 100%
-: 31:
1: 32: if (total != 45)
branch 0 taken 0% (fallthrough)
branch 1 taken 100%
#####: 33: printf ("Failure\n");
call 0 never executed
branch 1 never executed
branch 2 never executed
-: 34: else
1: 35: printf ("Success\n");
call 0 returned 100%
branch 1 taken 100% (fallthrough)
branch 2 taken 0% (throw)
1: 36: return 0;
-: 37:}So for each function, a line gets printed telling you how many times the function is called, how many times it returns, and what percentage of the function's blocks were executed. slay. 📊
For each basic block, a line gets printed after the last line of that basic block, describing the branch or call that ends it. And listen — there can be multiple branches and calls listed for a single source line, if multiple basic blocks end on that line. In that case, the branches and the calls each get given a number. 😌 There's no simple way to map those branches and calls back to source constructs, ngl. But in general? The lowest-numbered branch or call corresponds to the leftmost construct on the source line. iykyk.
For a branch: if it was executed at least once, you get a percentage — the number of times the branch was taken divided by the number of times it was executed. Otherwise you just get the message "never executed". 😭
For a call: if it was executed at least once, you get a percentage — the number of times the call returned divided by the number of times the call was executed. This is usually 100%, but it can be less for functions that call "exit" or "longjmp", because they might not return every single time they're called. fair. 💅
The execution counts are cumulative. So if the example program got executed again without removing the .gcda file, the count for how many times each line in the source was executed would get added to the results of the previous run(s). Which is lowkey super useful in a few ways — like, you could accumulate data over a number of program runs as part of a test verification suite, or get more accurate long-term info over a huge number of program runs. obsessed. 🌸
The data in the .gcda files gets saved immediately before the program exits. For each source file compiled with -fprofile-arcs, the profiling code first tries to read in an existing .gcda file; if the file doesn't match the executable (like, differing number of basic block counts), it just ignores the contents of the file. Then it adds in the new execution counts, and finally writes the data to the file. periodt. ✨
🎀 Using gcov with GCC Optimization 🎀
So if you're planning to use gcov to help optimize your code, you first have to compile your program with a special GCC option — --coverage. Aside from that, you can use any other GCC options you want. BUT — and this is the important bit, bestie — if you want to prove that every single line in your program was executed, you should not compile with optimization at the same time. 🚫
Why? On some machines the optimizer can eliminate some simple code lines by combining them with other lines. For example, code like this:
if (a != b)
c = 1;
else
c = 0;can get compiled into one instruction on some machines. And in that case, there is no way for gcov to calculate separate execution counts for each line, because there isn't separate code for each line. 😭 So the gcov output looks like this if you compiled the program with optimization:
100: 12:if (a != b)
100: 13: c = 1;
100: 14:else
100: 15: c = 0;The output shows that this block of code, combined by optimization, executed 100 times. In one sense that result is correct — there was only one instruction representing all four of those lines. However, the output does not indicate how many times the result was 0 and how many times the result was 1. 💀
Inlineable functions can also create unexpected line counts. Line counts get shown for the source code of the inlineable function, but what's shown depends on where the function is inlined, or if it isn't inlined at all. 🦋
If the function is not inlined, the compiler has to emit an out of line copy of the function, in any object file that needs it. So if fileA.o and fileB.o both contain out of line bodies of a particular inlineable function, they'll also both contain coverage counts for that function. And when fileA.o and fileB.o get linked together, the linker will — on many systems — select one of those out of line bodies for all calls to that function, and remove or ignore the other. Unfortunately, it will not remove the coverage counters for the unused function body. 😤 Hence, when instrumented, all but one use of that function will show zero counts.
If the function is inlined in several places, the block structure in each location might not be the same. For instance, a condition might now be calculable at compile time in some instances. And because the coverage of all the uses of the inline function gets shown for the same source lines, the line counts themselves might seem inconsistent. 🙈
Long-running applications can use the "__gcov_reset" and "__gcov_dump" facilities to restrict profile collection to the program region of interest. Calling "__gcov_reset(void)" clears all run-time profile counters to zero, and calling "__gcov_dump(void)" causes the profile information collected at that point to be dumped to .gcda output files. 📁
Instrumented applications use a static destructor with priority 99 to invoke the "__gcov_dump" function. So "__gcov_dump" is executed after all user defined static destructors, as well as handlers registered with "atexit". ✨
Heads up bestie: if an executable loads a dynamic shared object viadlopenfunctionality,-Wl,--dynamic-list-datais needed to dump all profile data. don't skip that one. 💅
The profiling run-time library reports various errors related to profile manipulation and profile saving. Those errors get printed into standard error output, or into the GCOV_ERROR_FILE file, if that environment variable is used. And if you want to terminate immediately after an error occurs, set the GCOV_EXIT_AT_ERROR environment variable. 🛑
That can help users find profile clashing, which leads to a misleading profile. so like, genuinely helpful, no cap. 🫶
👑 SEE ALSO 👑
gpl(7), gfdl(7), fsf-funding(7), gcc(1) and the Info entry for gcc.
💜 COPYRIGHT 💜
Copyright (c) 1996-2022 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 one's from gcc-12.5.0, dated 2025-07-11, and it's the GCOV(1) manual page. go forth and profile responsibly. 💖✨🎀
📦 where this page comes from
- ubuntu questing: gcc-12-arc-linux-gnu 12.5.0-6ubuntu1cross1
- ubuntu resolute: gcc-12-arc-linux-gnu 12.5.0-9ubuntu1cross1
- ubuntu stonking: gcc-12-arc-linux-gnu 12.5.0-9ubuntu1cross1
- 💖 girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms