public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/51883] Build warning unknown conversion type in gimplify.c
Date: Tue, 17 Jan 2012 16:24:00 -0000 [thread overview]
Message-ID: <bug-51883-4-tUUbViMAOQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51883-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51883
Manuel López-Ibáñez <manu at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |manu at gcc dot gnu.org
Resolution| |INVALID
--- Comment #1 from Manuel López-Ibáñez <manu at gcc dot gnu.org> 2012-01-17 16:12:55 UTC ---
GCC is built in stages. The first stage uses the system compiler, which may
have bugs or not handle special conversion type characters handled by the GCC
version being built (this particular warning). Therefore, warnings produced by
the system compiler are often wrong. Please, do not report them.
http://gcc.gnu.org/wiki/FAQ#stage1warnings
It would be nice to NOT produce any warning during stage 1, but I guess people
are happy enough just ignoring them to not bother sending a patch to fix the
build scripts. The build system of GCC is a huge complex mess, so one needs a
very good reason to play games with it.
next prev parent reply other threads:[~2012-01-17 16:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-17 15:42 [Bug c/51883] New: " mdblack98 at yahoo dot com
2012-01-17 16:24 ` manu at gcc dot gnu.org [this message]
2012-01-17 18:39 ` [Bug c/51883] " mdblack98 at yahoo dot com
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=bug-51883-4-tUUbViMAOQ@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).