On 06-06-2008 09:12:39 +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".
"-g -O2" is an autoconf default, used if you don't set CFLAGS, which is pretty much sane for a normal installation. If you want more, because you understand more (risk assessment, etc.) you can tweak your CFLAGS to suit your needs, e.g. "-march=native -pipe -O3" and way beyond that. That's how the autotools world works. > Moreover, there is the issue of performance experiments/comparisons in case > the default is not --enable-optimize . There is a difference between "user distribution" and "micro-detail-performance-experiment-hackery usage". The latter should be setup by someone who knows what he/she is actually doing. > Let try to make a final decision "life" during MADAM on Monday. ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Monetdb-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/monetdb-developers
