This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Standard scheme for maintainer-only debugging code?
- From: Richard Earnshaw <rearnsha at arm dot com>
- To: Andreas Schwab <schwab at suse dot de>
- Cc: DJ Delorie <dj at redhat dot com>, jbuck at synopsys dot com, jsm28 at cam dot ac dot uk, neroden at twcny dot rr dot com, gcc at gcc dot gnu dot org, Richard dot Earnshaw at arm dot com
- Date: Wed, 11 Jun 2003 10:27:20 +0100
- Subject: Re: Standard scheme for maintainer-only debugging code?
- Organization: ARM Ltd.
- Reply-to: Richard dot Earnshaw at arm dot com
> DJ Delorie <dj@redhat.com> writes:
>
> |> > Of course, there's a way to achieve both: debug_XYZ could be defined to
> |> > any of 0, 1, or flag_debug_XYZ, and there could be a single #ifdef to
> |> > make all of the flags variable.
> |>
> |> Perhaps enabled with --enable-maintainer-mode?
>
> IMHO this should not be overloaded. Debugging and maintaining are
> different concepts.
Especially since maintainer mode is supposed to bring additional
dependencies in the makefiles, that someone wanting to get debugging info
might not have to hand.
How about adding a "debug" check sub-option to --enable-checking?
R.