Fenrus Linux went to the RC on March 17th; the graphs at http://linux.fenrus.org/performance/ show that there's modest increases in the cray and graphics-magick tests, and a regression in fhourstones... with everything else being basically flat.
Phoronix: GCC 4.8 Release Brings Improved C++11, Optimizations
GCC 4.8 has been officially released today as the annual major update to the GNU Compiler Collection...
http://www.phoronix.com/vr.php?view=MTMzMzk
Fenrus Linux went to the RC on March 17th; the graphs at http://linux.fenrus.org/performance/ show that there's modest increases in the cray and graphics-magick tests, and a regression in fhourstones... with everything else being basically flat.
Quick question: when you say "support for new Broadwell instruction set", do you mean the compiler automatically chooses instructions from that instruction set when necessary ?
"Support for the new Intel processor codename Broadwell with RDSEED, ADCX, ADOX, PREFETCHW is available through -madx, -mprfchw, -mrdseed command-line options."
Not exactly what I meant... What I mean is if you enable the instructions, how does the compiler decide when to use them ? Because being specialized instructions, I don't see them being used for things like conditionals and simple math operations which are the most common used operations in a program. What I really mean is that everytime I have seen code optimized for a specific processor instruction set, the coding is done in assembler, not using a c/c++ compiler...
go gcc!!!
To hell with clang!!!
Fuck apple!!!
The Prefetch instruction (and in this case "prefetchw") is almost always a loss. Hardware nowadays has pretty aggressive prefetchers that work on the actual access pattern, and those are very effective for most cases.
The problem is that for the cases where it's not (e.g. the ones hard to tell by a machine) are also the ones where the compiler will have a hard time adding their own prefetches. (there are some special cases in HPC and such where the human can know special things)
it's branch prediction hints all over again in many ways, where a broad use is damage because programmers know their own program not as well as the cpu does ;-)