It says
Note: `tcc` was not used, so unless you install it yourself, your backend C compiler will be `cc`, which is usually either `clang`, `gcc` or `msvc`.
Also you have "gcc" in your error:
See <file:///usr/share/doc/gcc-7/README.Bugs>
And on the website the claim is made for tcc and x64 backends.
Like I said, no way it'd take 15 seconds :)
I think it's pretty clear.
Anyway, now that we are clear on the compilation speed claim, can you please list a couple of those extraordinary claims?
(This is my final response on this matter. I have already given enough information and an inability to interpret it is not my business.)
I've just tested it, and turns out all C compilers are terrible at hundreds of thousands of print calls (for me Clang was stuck for minutes with 100% cpu usage).
The claim was made about actual code, like the V compiler itself, which is about 220k loc and compiles in 0.3 seconds, not some unrealistic test with a million of prints.
I'll make it clear on the home page with a link to the benchmark.
You don't have to guess because I can give you my log. I have exactly followed what the OP did, except for more recent revision because I couldn't get it compiled in my environment.
I have also verified that TCC was indeed in use: (I gave up when the gcc memory usage ballooned up to 20 GB.)> What's your hardware? CPU/SSD.
i7-7700 3.60 GHz, 48 GB of RAM, SSD in use, Windows 10 WSL (that's probably why kernel time is higher than average, otherwise my userland time agrees with the OP).