News for hackers. Stuff that matters.

A comment on Intel's “cripple AMD” function (2019). Parent comment

Re:Intel's “cripple AMD” function (2019) by physicsguy on Saturday August 29, 2020 @05:26AM (#24314872)
For what sort of application? I ran benchmarks of my own scientific code for doing particle-particle calculations and with -march=native I could get 2.5x better performance with Intel vs GCC.

One thing I found that you do have to be careful with though is ensuring that Intel uses IEEE floating point precision, because by default it's less accurate than GCC. This causes issues in Eigen sometimes, we ran into an issue recently after upgrading compiler where suddenly the results changed and it was because someone had forgotten to set 'fp-model' to 'strict'

[ Parent | on HN ]
Re:Intel's “cripple AMD” function (2019) by bluecalm on Saturday August 29, 2020 @06:32AM (#24315147)
If Intel is using floating point math shortcuts you can replicate it with -Ofast when using gcc.

It goes without saying that you should use -O3 (or -O2 for some rare cases) otherwise. I am mentioning it just in case because 2.5x slower sounds so exotic to me that the first intuition is that you're omitting important optimization flags when using GCC. GCC was faster than Intel on everything I tried in the past.

[ Parent | on HN ]