From: "Vincent Rivière" <vincent.riviere@freesbee.fr>
To: gcc@gcc.gnu.org
Subject: Re: Endless "declared 'static' but never defined" warnings with stage 2 & 3 compilers
Date: Sun, 01 Jul 2012 16:53:00 -0000 [thread overview]
Message-ID: <4FF0807D.5010809@freesbee.fr> (raw)
In-Reply-To: <463F5883-4834-49CA-A123-7A26D9BA0377@gmail.com>
On 01/07/2012 16:16, t-rexky wrote:
> I discovered that if I rebuild stage 3 with BOOT_CFLAGS="-g -O0", the
> warnings in stage 3 compiler all disappear!
This is extremely wierd!
So it looks like something is affected by the optimization level. Usually,
it is an uninitialized variable, buffer overflow, strict aliasing issue, or
maybe a GCC bug...
Since it is unlikely that this specific bug is in the standard GCC sources
(other people would have noticed), maybe it could be somewhere in the C
sources added for your NeXT configuration?
--
Vincent Rivière
next prev parent reply other threads:[~2012-07-01 16:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-11 19:20 t-rexky
2012-06-12 12:03 ` Vincent Rivière
2012-06-18 3:54 ` t-rexky
2012-07-01 14:17 ` t-rexky
2012-07-01 16:53 ` Vincent Rivière [this message]
2012-07-08 12:32 ` t-rexky
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=4FF0807D.5010809@freesbee.fr \
--to=vincent.riviere@freesbee.fr \
--cc=gcc@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).