John Mandereau <john.mander...@gmail.com> writes: > I wonder why Patchy has unconditionnally run configure with > --disable-optimising since last December or so.
Because without that, compilations get run with -DNDEBUG and assertions are not tested. Also some other tests (like that for parsed objects that should be dead) are not being run. <URL:http://code.google.com/p/lilypond/issues/detail?id=1905> <URL:http://code.google.com/p/lilypond/issues/detail?id=1908#c3> > I guess there used to be issues with optimisation for some GCC > versions. Could optimisations be enabled again now? Or better, could > we allow developers who run Patchy tune configure flags? > > I'm asking this because I suspect the Pentium 4 at MSH Paris Nord > could build the docs significantly faster by building LilyPond with > appropriate GCC flags, instead of building a binary for a generic x86 > processor. The problem is not actually the optimization setting, but the debug code. -- David Kastrup _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
