public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joe Buck <Joe.Buck@synopsys.com>
To: "H.J. Lu" <hjl.tools@gmail.com>, GCC Development <gcc@gcc.gnu.org>
Subject: RE: Bootstrap with -Wmissing-prototypes doesn't work for C++
Date: Fri, 19 Aug 2011 19:25:00 -0000	[thread overview]
Message-ID: <59662D5BB74CD84D9FA8E6491ADB51A7DEAE4D4D@US01WXMBX1.internal.synopsys.com> (raw)
In-Reply-To: <CAMe9rOqKLAhNGY0oHqEU8HKuP-N1SLKHOe=pykJS8ZR3JcF9aw@mail.gmail.com>

I'm confused. Since C++ treats the lack of a prototype as a hard error, what does it mean to make -Wmissing-prototypes useless?

________________________________________
From: gcc-owner@gcc.gnu.org [gcc-owner@gcc.gnu.org] On Behalf Of H.J. Lu [hjl.tools@gmail.com]
Sent: Friday, August 19, 2011 9:36 AM
To: GCC Development
Subject: Bootstrap with -Wmissing-prototypes doesn't work for C++

Since -Wmissing-prototypes doesn't work for C++, using
C++ to bootstrap GCC makes -Wmissing-prototypes useless.
You will see the -Wmissing-prototypes message in stage 1,
but you won't see it in stage3 2/3.

--
H.J.

  reply	other threads:[~2011-08-19 19:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-19 16:36 H.J. Lu
2011-08-19 19:25 ` Joe Buck [this message]
2011-08-19 19:34   ` H.J. Lu
2011-08-19 20:35     ` Paul_Koning
2011-08-19 20:42       ` H.J. Lu
2011-08-19 21:45     ` Ian Lance Taylor
2011-08-19 21:58       ` H.J. Lu
2011-08-19 22:43       ` Gabriel Dos Reis
2011-08-20  4:18         ` Ian Lance Taylor
2011-08-20  5:20           ` Gabriel Dos Reis
2011-08-20 14:21             ` Ian Lance Taylor
2011-08-21 23:48               ` Joe Buck
2011-08-19 21:47   ` Marc Glisse

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=59662D5BB74CD84D9FA8E6491ADB51A7DEAE4D4D@US01WXMBX1.internal.synopsys.com \
    --to=joe.buck@synopsys.com \
    --cc=gcc@gcc.gnu.org \
    --cc=hjl.tools@gmail.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).