Milestones

[acmnpv]

Hej,
I have recently seen the milestones for the development and was wondering why you want to kill the optimisation for the tools?

Thanks for answering

Paul

[amrein]

Hi,
Because its a particularly bad idea to trade accuracy for speed in the tools.
They are fast enough without optimizations. One could discuss -O1 and for some compilers -O2.
But -O3 or -xhost is a very bad idea.

[acmnpv]

Ok, I will make the test to see if there are differences between the different optimisations.

[esguerra]

Just echoing what Beat points out from the standard from gcc:

"-O0 Reduce compilation time and make debugging produce the expected results. This is the default. "

https://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html

[esguerra]

Reading a bit further:
"-Og Optimize debugging experience. -Og enables optimizations that do not interfere with debugging. It should be the optimization level of choice for the standard edit-compile-debug cycle, offering a reasonable level of optimization while maintaining fast compilation and a good debugging experience."

[acmnpv]

Sure, for debugging I have the optimisations turned off. But I just made two versions of Qfep, one with -O3 in gfortran and one with -O0, and both are giving identical results.
So I really don't get what is this about. If you are having issues with optimised binaries, please tell me and I can fix the underlying bugs.

[amrein]

Absolutely, and what about the other tools, did you try them with different architectures (eg the same executable on akka+abisko+triolith+tintin)?
And more importantly: Would you mind to tell us, what the timing differences you obtaind are?