From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sourceware.org
Subject: Re: RFC: Use -Wall -Wextra
Date: Fri, 29 Dec 2006 12:13:00 -0000 [thread overview]
Message-ID: <uzm963noj.fsf@gnu.org> (raw)
In-Reply-To: <20061228195533.GA18492@nevyn.them.org> (message from Daniel Jacobowitz on Thu, 28 Dec 2006 14:55:33 -0500)
> Date: Thu, 28 Dec 2006 14:55:33 -0500
> From: Daniel Jacobowitz <drow@false.org>
>
> I'd like to hear opinions on this patch. It changes the default set of GDB
> build warnings from:
>
> build_warnings="-Wimplicit -Wreturn-type -Wcomment -Wtrigraphs \
> -Wformat -Wparentheses -Wpointer-arith -Wformat-nonliteral \
> -Wunused-label -Wunused-function -Wno-pointer-sign"
>
> to:
>
> build_warnings="-Wall -Wextra -Wpointer-arith -Wformat-nonliteral \
> -Wno-pointer-sign -Wno-unused-parameter \
> -Wno-unused -Wno-sign-compare -Wno-switch -Wno-missing-field-initializers"
I would agree only if we never try to use -Werror, because with such
aggressive warnings GDB will never build if we add -Werror.
My other fear is that, with GCC becoming more and more picky about
perfectly valid C code, these options will cause the compilation to
become very noisy, but I guess we will hear complaints if that
happens.
> I'd really like to turn on -Wunused too, but it has been off for so long
> that we have a substantial number of unused local variables - it will take
> some work to clean up.
I'd advise against -Wunused: the problems it finds are harmless,
whereas fixing them is not trivial at all, and quite ugly in some
cases.
> Index: doc/gdbint.texinfo
> ===================================================================
> RCS file: /cvs/src/src/gdb/doc/gdbint.texinfo,v
> retrieving revision 1.247
> diff -u -p -r1.247 gdbint.texinfo
> --- doc/gdbint.texinfo 10 Nov 2006 19:20:37 -0000 1.247
> +++ doc/gdbint.texinfo 28 Dec 2006 19:39:07 -0000
This is fine with me, thanks.
next prev parent reply other threads:[~2006-12-29 12:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-28 19:55 Daniel Jacobowitz
2006-12-29 12:13 ` Eli Zaretskii [this message]
2006-12-29 13:58 ` Daniel Jacobowitz
2006-12-29 20:44 ` Eli Zaretskii
2006-12-29 21:02 ` Daniel Jacobowitz
2006-12-30 15:32 ` Eli Zaretskii
2006-12-30 16:00 ` Daniel Jacobowitz
2006-12-30 16:55 ` Eli Zaretskii
2007-01-03 19:12 ` Daniel Jacobowitz
2007-01-03 20:38 ` Mark Kettenis
2007-01-04 4:09 ` Eli Zaretskii
2007-01-04 19:42 ` Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=uzm963noj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox