On Fri, Jun 06, 2008 at 09:12:39AM +0200, Stefan Manegold wrote:
On Fri, Jun 06, 2008 at 08:59:35AM +0200, Fabian Groffen wrote:
On 06-06-2008 08:49:45 +0200, Niels Nes wrote:
On Fri, Jun 06, 2008 at 08:28:10AM +0200, Stefan Manegold wrote:
[...]
It would make sense to me if the nightly tarballs, which include the superballs all compile with strict, optimize and assert being *disabled* by default, for a sane code distribution.
Please note that for some compiler issues to catch, one has to use -O2 (--enable optimize?), however doing that makes the binary hard to debug, which results in a natural inconvenience here...
Even without --enable-optimize the configure default (not our choice, but that of the makers of configure!) (at least for gcc, not the most rare compiler) is "-g -O2", hence, the default does not omit "-O2".
Moreover, there is the issue of performance experiments/comparisons in case the default is not --enable-optimize . Let try to make a final decision "life" during MADAM on Monday.
Of course, until then, suggestions, ideas, concers, etc. as input for the desicion are more than welcome to be shared and discussed on this list!
Stefan