On: Beating the Compiler

[flukus]

> I also wish I knew what optimization settings GCC/etc was using, and what effect tweaking those has.

From the makefile:

GCCFLAGS = -O3 --std=c++11

MSFLAGS = /nologo /Ox /Ob2 /Ot /Oi /GL

[Too → flukus]

Would march=native and fstrict-aliasing do any difference?

It would be interesting to compare the compiled asm with the hand rolled one.

The code has some potential improvements also but maybe the compiler is smart enough to find them, such as reading pivot.key in the loop even though it doesn't change.

[haldean → Too]

-march=native would almost certainly help, but I'm pretty sure -fstrict-aliasing is the default.