From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: pkoning@equallogic.com
Cc: gdb@sources.redhat.com
Subject: Re: -Wall
Date: Wed, 31 Aug 2005 19:33:00 -0000 [thread overview]
Message-ID: <200508311932.j7VJWBLL003494@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <17173.64766.911558.85264@gargle.gargle.HOWL> (message from Paul Koning on Wed, 31 Aug 2005 14:54:54 -0400)
> Date: Wed, 31 Aug 2005 14:54:54 -0400
> From: Paul Koning <pkoning@equallogic.com>
>
> Gdb (6.3 at least) generates a bunch of warnings when compiled with
> -Wall (or a similar set of "warn for everything I can think of"
> switches that are popular around here).
>
> Would patches to cure these be welcome?
>
configure.ac has this note:
# NOTE: Don't add -Wall or -Wunused, they both include
# -Wunused-parameter which reports bogus warnings.
so currently GDB has its own set of warning flags, currently:
build_warnings="-Wimplicit -Wreturn-type -Wcomment -Wtrigraphs \
-Wformat -Wparentheses -Wpointer-arith -Wformat-nonliteral \
-Wunused-label -Wunused-function"
Further down there is:
# Up for debate: -Wswitch -Wcomment -trigraphs -Wtrigraphs
# -Wunused-function -Wunused-variable -Wunused-value
# -Wchar-subscripts -Wtraditional -Wshadow -Wcast-qual
# -Wcast-align -Wwrite-strings -Wconversion -Wstrict-prototypes
# -Wmissing-prototypes -Wmissing-declarations -Wredundant-decls
# -Woverloaded-virtual -Winline -Werror"
which probably qualifies as "warn for almost everything I can think
of". The main reason for not enabling those is that there is still
too much shoddy code in GDB that triggers these, making -Werror
basically unusable. But I'd certainly welcome patches to remove
warnings on that list.
The best thing to do would probably be to target the options one at a
time and then add the corresponding -W to the list used by GDB.
Mark
next prev parent reply other threads:[~2005-08-31 19:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-31 18:55 -Wall Paul Koning
2005-08-31 19:33 ` Mark Kettenis [this message]
2005-08-31 19:56 ` -Wall Stan Shebs
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=200508311932.j7VJWBLL003494@elgar.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=gdb@sources.redhat.com \
--cc=pkoning@equallogic.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).