On 2012-12-26 19:04, Volker Braun wrote: > * SAGE_DEBUG=no means no debugging symbols (no gcc -g), which > basically only saves disk space. > > * SAGE_DEBUG=yes builds debug versions if possible (in particular, > Python and Singular). These will be notable slower but allow us to > pinpoint memory problems much more easily. > > * Anything else (including unset SAGE_DEBUG) is the same as the old > default, compile with debugging symbols but no debugging options that > influence performance. Good idea!
Let me add that the GCC spkg also implements SAGE_DEBUG=yes by building a slower compiler with more internal checks (but the programs generated by GCC are the same). -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-devel?hl=en.
