On Sun, Dec 9, 2012 at 3:44 PM, Diego Elio Pettenò <flamee...@flameeyes.eu> wrote: > On 09/12/2012 17:32, NightStrike wrote: >> It's not more fully documented elsewhere, though. AM_CPPFLAGS right >> about it is, however, fully documented right in this section. This >> should be fixed, since nowhere does the manual say that AM_CFLAGS is >> "-g -O2" by default. > > Is it? I was confident that AM_CFLAGS is unset by default, but CFLAGS > (from autoconf) is "-g -O2" by default. > > And no you shouldn't change CFLAGS in configure.ac, please. That's an > user-assignable variable, distributions cry every time that we have to > patch a CFLAGS="$something" in configure.ac. Especially when that's to > set/unset -O and -g flags depending on a debug/release build (hint: > distributions want debug information with optimized builds as well!). Seems reasonable (otherwise a stack trace is useless). Also, it does not affect performance. Confer: "How does the gcc -g option affect performance?" http://gcc.gnu.org/ml/gcc-help/2005-03/msg00032.html.
Jeff
