So looks like this thread is more suitable for false positive virus complains, compatibility with Windows XP, missing dll and such. People should post comparisons in another thread.

Build for @sundance.

Converting: "F:\Testdir\BLove.wav"
Destination: "F:\[unnamed]\[unnamed]\- BLove.flac"
CLI encoder: flac.exe
Destination file: F:\[unnamed]\[unnamed]\- BLove.flac
Encoder stream format: 44100Hz / 2ch / 16bps
Command line: "C:\Program Files (x86)\foobar2000\encoders\flac.exe" -s --ignore-chunk-sizes -7 - -o "temp-4CDF95EB111ABB419B7B2E665CF02BDD.flac"
Working folder: F:\[unnamed]\[unnamed]\
Encoder process still running, waiting...
Encoder process terminated cleanly.
Track converted successfully.
Total encoding time: 0:28.140, 168.12x realtime

Converting: "F:\Testdir\BLove.wav"
Destination: "F:\[unnamed]\[unnamed]\- BLove.flac"
CLI encoder: flac.exe
Destination file: F:\[unnamed]\[unnamed]\- BLove.flac
Encoder stream format: 44100Hz / 2ch / 16bps
Command line: "C:\Program Files (x86)\foobar2000\encoders\flac.exe" -s --ignore-chunk-sizes -7 - -o "temp-698D0D3FBED8A347829C6247F55987F4.flac"
Working folder: F:\[unnamed]\[unnamed]\
Encoder process still running, waiting...
Encoder process terminated cleanly.
Track converted successfully.
Total encoding time: 0:23.828, 198.54x realtime

Here's another 1.4.1 compile with newer GCC (12.2.0). Over here it's faster than Xiph build even with -p.

You use gcc with tunings 'haswell'. Can you please build one with tunings 'zenv3' if you find some time?
I really wonder what the tunings do these days on my Ryzen.

Quote from: Wombat on 2022-09-25 15:33:48

You use gcc with tunings 'haswell'. Can you please build one with tunings 'zenv3' if you find some time?
I really wonder what the tunings do these days on my Ryzen.

Here's a fresh compile with 'znver3' tuning.

Thank you for this! I’m not sure I truly understand the technical details behind it but if I have the gist of it correct, this build would be somehow optimized for Zen 3 CPUs eg. 5950X?

Quote from: MrRom92 on 2022-09-25 21:42:02

Thank you for this! I’m not sure I truly understand the technical details behind it but if I have the gist of it correct, this build would be somehow optimized for Zen 3 CPUs eg. 5950X?

A program like FLAC is simply a set of instructions that a CPU should follow. One can imagine that like food where one can take several ways to cook the same dish, there are a lot of ways CPUs can be instructed to do the same thing.

FLAC is written in C, a programming language. To obtain a program, one uses a compiler, which translates code into a program. The compiler has some liberties in this translation that do not affect the result, but do affect the speed of execution.

Now, a new CPU like the Zen 3 CPUs has a lot more instructions than an old CPU like the first Intel Pentium processor (which came out in 1993). The basis is the same, but a new CPU has additions that are mentioned quite often in this context, like SSE and AVX. A compiler can be instructed to generate a binary that runs on old CPUs too, but then it can't use new instructions that old CPU doesn't have. When compiling specifically for a certain CPU, the compiler can choose from all possible instructions, some of which may be much faster than using common ones the old CPU has too.

Furthermore, some instructions are fast and some are slow. How fast and how slow, that differs per CPU. If a compiler can choose two ways to translate some bit of code, by default it chooses a compromise: something that isn't too slow on all targeted CPUs. However, when tuned for a specific CPU, the compiler knows which instructions to avoid (because they are slow on that specific CPU) and can create a faster program.

These two things can be combined. You can make a binary that runs on all CPUs (including the old Pentium) but is tuned specifically for a certain CPU. Then the compiler doesn't use new instructions, but only takes the certain CPU into account when choosing between possibilities offered by those instructions. One can also instruct the compiler to use the instructions offered by a certain CPU, but not tune for that CPU specifically (so, use instructions offered by Intel CPU x, but keep AMD CPUs with the same capabilities in mind when making decisions). One can also do both: use instructions of and tune for a certain CPU.