Neil Puttock <[email protected]> writes: > On 19 September 2011 15:10, [email protected] <[email protected]> > wrote: > >> Also, it may be worth it to consider scrapping optimized binary >> altogether - it'd be good to test how much overhead the unoptimized >> version introduces with respect to the optimized version. > > Eek, you don't want to do that. The unoptimized build's bloated by > debug symbols and runs much slower in my experience.
The debug symbols should not affect code speed, and they are present in the unoptimized build, anyway, unless you are talking about something completely different from what I think you do. I find it disturbing, however, that our default build uses NDEBUG to disable assertions. Under normal circumstances, assertions have negligible speed impact. It makes little sense to restrict their use explicitly to non-optimized builds. In particular since it makes it quite unlikely that one can catch Heisenbugs with assertions: they often go away with significant code changes, and switching optimization off most certainly _is_ a significant change. -- David Kastrup _______________________________________________ bug-lilypond mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-lilypond
