I hope it happens for every single PKGBUILD.
Originally Posted by Welsh Dwarf
Do you think Arch will switch to EKOPath any time soon?
They didn't switch to systemd, so I doubt if they'll switch to EKOPath soon.
Originally Posted by Viper_Scull
This was for freebsd. This time it's different, so I hope they'll choose a GPL.
Originally Posted by clavko
Verry impressive results. But those results do remind me of the "compiler deathmatch" use the search function to find it. In that deathmatch gcc could be made A LOT faster than the stock settings. Archlinux four example it's using roughly the stock compiler settings. If this new compiler is just by default having all those optimizing things turned on than the current phoronix comparisons aren't even fair..
Just my 5 cents..
Gentoo guys will mostly tell you to stick to -march-native -O2 -pipe, anything more aggressive leads to breakage somewhere.
Originally Posted by markg85
Aggressive optimisations should be used per-package, when you know that they won't break a particular package.
Any compiler guys around to tell whether a 2-3x increase like this over latest gcc is considered possible/doable? I was under the impression it's already very good, with icc only gaining 10-30% and visual studio less.
In some cases it also leads to slower performance.
Originally Posted by pingufunkybeat
I personally find it very unlikely, which is why I'm leaning towards this being about a cpu+gpu compiler. I haven't seen icc reach anything near 2x against gcc/llvm in my (admittedly few) benchmark tests so I doubt ekopath would be able to generate so much better code as to result in 2x, 2.3x better performance (although it sure would be awesome!). As for Visual Studio, last time I benchmarked it against GCC, GCC generated faster code for Mame atleast (which was the only test I did), but that was VS 2008 though.
Originally Posted by curaga
Weird that sqlite has problems with -Ofast (assuming that it works with -O3) since -Ofast only turns on -ffast-math and I can't see why sqlite would depend on high-precision for it's floating point math.
Originally Posted by FireBurn
As for -Os, it prefers code size over code speed, so unless you are starved for ram I would suggest using -O2 where -O3 causes problems rather than -Os.
Tags for this Thread