News for hackers. Stuff that matters.
Re:Beating the compiler by richardwhiuk on Sunday March 22, 2015 @05:02PM (#9248209)
Of course, the next step is obvious - work out why the compiler didn't do a four way avx unroll, and then submit a bug fix to clang to make it do that. That way all of your future code benefits from your single micro-optimization.

It's also possible that you find out that if you enable --generate-for-haswell or some other arcane compiler flag, it'll do it for you.

Re:Beating the compiler by pbsd on Sunday March 22, 2015 @05:19PM (#9248289)
All the author had to to was to add '-march=native' or '-march=core-avx2' to the compiler command line: http://goo.gl/H4f62I
Re:Beating the compiler by jevinskie on Sunday March 22, 2015 @06:18PM (#9248495)
Clang 3.7.0 (experimental) + -march=skylake gives you AVX512. zmm all the way, baby! 256 bytes processed in the inner loop!
Re:Beating the compiler by pantalaimon on Sunday March 22, 2015 @08:38PM (#9248877)
But what gives me a Skylake CPU?
Re:Beating the compiler by duskwuff on Sunday March 22, 2015 @11:51PM (#9249422)
A time machine, or a job working at Intel? :)