From: "Theodore A. Roth" <troth@openavr.org>
To: gdb@sources.redhat.com
Subject: suggested compile warnings
Date: Fri, 23 May 2003 19:09:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.53.0305231130230.32235@knuth.amplepower.com> (raw)
Hi,
I've always been configuring gdb with --enable-gdb-build-warnings=-Werror
and thought that there where a bunch of gcc compile warnings issued.
Looking more closely at my builds, that doesn't seem to be true.
For my own apps, I like to use '-Wall -Werror' as it lets the compiler
catch a lot of my stupid mistakes. I tried '-Wall -Werror' for gdb,
but that seems to be too restrictive for gdb source.
Does anyone else compile gdb with any of the -W<foo> gcc options?
Is there a recommended list of these which should be used?
For example, adding -Wunused (without -Werror), turns up 149 wanrings.
Most are unused variables, some are static decl's for functions that
aren't defined. Most if not all of these should be trivial to fix.
Ted Roth
next reply other threads:[~2003-05-23 19:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-23 19:09 Theodore A. Roth [this message]
2003-05-23 20:17 ` Andrew Cagney
2003-05-23 21:02 ` Theodore A. Roth
2003-05-23 21:17 ` David Carlton
2003-05-23 21:46 ` Andrew Cagney
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=Pine.LNX.4.53.0305231130230.32235@knuth.amplepower.com \
--to=troth@openavr.org \
--cc=gdb@sources.redhat.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).