The default Optimization level of open64 is -O2 .. if you specify nothing you get O2's.
In other words: The "-march=bdver1" are with O2 ;)
+ quote from the article:
The options tested included stock (not overriding any CFLAGS/CXXFLAGS and Open64 defaults to the -O2 optimization level)
I have previously mentioned this in the forums and not surprisingly Michael didn't comment. However, a fanatic-sounding guy jumped at me that I shouldn't expect Michael to be my brain-prosthesis - or something like that. :P
I think this kind of articles are driving down the quality of Phoronix and make it similar content-mills.
somebody explain - what is the point of measuring time TO COMPILE a piece of software?
it's obvious that more aggressive optimizations will increase build time, and -O0 will be the fastest.
my idea of benchmarking a compiler would be to measure build time of a source package with DIFFERENT BUILDS of the same compiler under the same CFLAGS, not comparing different cflags against the same build of compiler.
Actually you have a point that compile time is a relatively "boring" measure since it probably has less impact on the choice of compiler (although you might want to have a fast compiler during development and then a really good optimizing one for when you want to distribute binaries). The interesting measures would be:
* size of the resulting binaries
* performance of the resulting binaries