AMD Compiler Optimization Benchmarks With GCC 4.10 (GCC 5.0)
Phoronix: AMD Compiler Optimization Benchmarks With GCC 4.10 (GCC 5.0)
As a continuation to yesterday's brief GCC 4.9 vs. GCC 4.10 (GCC 5.0) comparison with the AMD A10 A-Series "Kaveri" APU, here's some benchmarks when using the GCC 4.10 development snapshot and trying a variety of CFLAGS/CXXFLAGS to see the current impact on their performance for a variety of Linux benchmarks...
And with the Default settings that each Distro uses?
I looked in the GCC docco and it seemed to suggest that there was no "default" setting, which surprised me at first but I guess makes sense. That means distros would actually have to pick a CPU for each build though.
Originally Posted by Nille
The default that distros use is -march=x86-64 -mtune=generic -O2. No need to pick a specific CPU.
Originally Posted by bridgman
Nille, the article is about new compiler developments and not about distros. You will not find a distro that ships 4.10 out of the box. The article is meant to give an outlook on what is coming in terms of new optimizations with the next major version of gcc.
Originally Posted by Nille
Trying to run benchmarks with a prerelease of gcc-4.10 and the compiler options the distros use is ... like trying to compare people of different countries based on their perfomance in driving a new car's unfinished prototype. It would be as stupid as the European Song Contest.
Each distro has got a different opinion on what is best for their users. Many distros sacrifice a bit of performance for getting more security. When they use the stack-protector feature of gcc and also write-protect code segments through linker options for example. You would be comparing apples to oranges and the result would only draw a false picture. Some people would start believing "distro A" is worse than "distro B", only because it is slower, but they would not actually know where this difference is coming from. It leads to bad, uninformed opinions.
In general, if it is important to you that a piece of software runs very fast then try to recompile the package or get the original code. This way you can target the optimizations directly at your specific hardware (i.e. with -march=native), which a distro cannot do, because they always need to keep the code compatible to as many processors as possible. You can also disable options and features of a package, because many distros try to enable as many features as possible, while most people do not need every single feature. However, the distros need to do this so that as many people as possible can find a package useful. Hence trimming down the features can make code more compact and faster, too.
If it is still not fast enough then you will probably already know that your hardware is too slow and you would only be trying to blame the software for it.
It's time to learn Gentoo?
Can always learn Antergos(Arch Linux). Compiling with compiler flags is a matter of modifying /etc/makepkg.conf with your preferences and compiling software from the repos with yaourt. yaourt -Sb for official packages and yaourt -S for packages from the AUR.
Originally Posted by souenzzo
I once thought that, too. Then I benchmarked my bulldozer: mtune=generic vs. march=native. And guess what? There was no difference! That's why I'd like to see mtune =generic in these benchmarks, too. After all, this is what you'll roughly get from the distributions.
Originally Posted by sdack
Last edited by oleid; 08-16-2014 at 04:50 PM.
-mtune= only selects the CPU type for instruction scheduling. -march= selects the CPU type for the instructions to use.
Originally Posted by oleid
This certainly makes a difference, but it does not show with just every application. This is what the article is trying to present by the way. For example -march=k8 will select the standard x86 instruction set up to and include SSE2, -march=amdfam10 will further include SSE3 and SSE4A instructions, and -march=bdver1 will also include SSE4.1, SSE4.2 and AVX instructions.
Whereas -mtune=k8 will tell the compiler to schedule instructions for a L1=64k/L2=512k configuration and that moving an MMX/SSE register to integer has got a cost of 5. Using -mtune=amdfam10 will make it use the same L1/L2 configuration, but sets the cost of MMX/SEE to integer conversions down to 3. And -mtune=bdver1 will use L1=16k/L2=2048k for cache sizes and sets the cost down to 2.
There are a lot more parameters hidden behind these switches. These are just some of the parameters used by GCC to make its decisions. The parameter "generic" will simply pick good, average values for all of these parameters. The differences will not show unless you know what exactly to look for and by choosing an application that you know of will benefit significantly from it. Only with very precise benchmarking tools and setups can one also detect the difference this makes for other applications. The result will usually vary so much, that one needs to make many runs before a clear difference becomes visible, because these will only be tiny and the variations will add a lot of noise into the measurements. Hence the focus on ImageMagick and C-Ray.
What makes this special for gcc is that it is not a simple thing to just turn code into machine instructions. The compiler needs to detected patterns in the code before it can decide to use the newer SSE4 and AVX instructions over the older MMX/SSE/SSE2 ones. And putting this into a compiler and making it use every new, last feature of new CPUs is a challenge.
Last edited by sdack; 08-16-2014 at 05:59 PM.
Originally Posted by sdack
Tags for this Thread