From: Tom Tromey <tromey@redhat.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Fix most -Wmissing-prototypes -Wmissing-declarations warnings
Date: Wed, 18 Feb 2009 22:54:00 -0000 [thread overview]
Message-ID: <m3ocwzzf5g.fsf@fleche.redhat.com> (raw)
In-Reply-To: <200902180201.05118.pedro@codesourcery.com> (Pedro Alves's message of "Wed\, 18 Feb 2009 02\:01\:04 +0000")
>>>>> "Pedro" == Pedro Alves <pedro@codesourcery.com> writes:
Pedro> With all the latest talk about declarations and prototypes, I
Pedro> got curious and tried building GDB on x86_64-linux with
Pedro> `-Wmissing-declarations -Wmissing-prototypes' added to
Pedro> WARN_CFLAGS, like so:
Nice. I'm in favor of going this route. It seems to me that this can
catch real bugs and doesn't really have a downside.
Pedro> E.g., notice that a few functions here are really unnused and
Pedro> should probably either be deleted, or there's a bug hiding in
Pedro> there: e.g., i386-nat.c:child_post_startup_inferior or
Pedro> ada-typeprint.c:ada_typedef_print.
The ada_typedef_print thing is a known oddity:
http://sourceware.org/ml/gdb-patches/2008-09/msg00541.html
I was hoping an Ada maintainer would deal with this.
Pedro> I've also tried adding "-Wmissing-prototypes", but it shows up a
Pedro> few more issues than I have energy at the moment to look at.
Did you mean some other option here?
Tom
next prev parent reply other threads:[~2009-02-18 20:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-18 4:11 Pedro Alves
2009-02-18 4:12 ` Pedro Alves
2009-02-18 14:27 ` Mark Kettenis
2009-02-18 17:34 ` Pedro Alves
2009-02-20 0:09 ` Mark Kettenis
2009-02-22 11:19 ` Pedro Alves
2009-02-18 22:54 ` Tom Tromey [this message]
2009-02-20 0:46 ` Joel Brobecker
2009-02-20 4:01 ` Tom Tromey
2009-02-20 5:43 ` Tom Tromey
2009-02-20 10:02 ` Joel Brobecker
2009-02-22 1:06 ` Pedro Alves
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=m3ocwzzf5g.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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