4 ms·
Interesting. So how does this set of options tend to differ from those used by the guys who build the normal binary packages?
by mac01021 9y ago
Interesting.
So how does this set of options tend to differ from those used by the guys who build the normal binary packages?
- giancarlostoro 9y agoThey probably compile it with generic flags to support x86 or x64 for having more than a handful of package repositories for different architectures, as opposed to having hundreds / thousands of package repositories for every processor released out there. When a package is compiled down to your specific processor it is not guaranteed at all to run on another system. This is also done by people who use Gentoo as well as other source based distributions.
- jcelerier 9y agoDefault is CFLAGS="-march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -fno-plt" CXXFLAGS="-march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -fno-plt" LDFLAGS="-Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now" which ensure that it would still work with an AMD Athlon64 from 2003, but you don't get any "new" things such as SSE4, AVX, etc. unless the developer hand-codes specific cases for these CPUs.