From: Andreas Jaeger <aj@suse.de>
To: gcc@gcc.gnu.org
Subject: Bootstrap broken in Mainline
Date: Tue, 21 Sep 2004 09:18:00 -0000 [thread overview]
Message-ID: <hoy8j4gjuk.fsf@reger.suse.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 890 bytes --]
With current CVS I get a bootstrap error in cp/decl.c on Linux/AMD64:
cc1: warnings being treated as errors
/cvs/gcc/gcc/cp/decl.c: In function 'reshape_init':
/cvs/gcc/gcc/cp/decl.c:4162: warning: 'max_index_cst' may be used uninitializedin this function
make[2]: *** [cp/decl.o] Error 1
The code is basically:
HOST_WIDE_INT max_index_cst;
if (sized_array_p)
/* HWI is either 32bit or 64bit, so it must be enough to represent the
array size. */
max_index_cst = tree_low_cst (max_index, 1);
for (index = 0;
*initp && (!sized_array_p || index <= max_index_cst);
++index)
So, this looks like some wrong warning - but we fix it somehow.
Andreas
--
Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj
SUSE Linux AG, Maxfeldstr. 5, 90409 Nürnberg, Germany
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
next reply other threads:[~2004-09-21 7:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-21 9:18 Andreas Jaeger [this message]
2004-09-21 9:24 ` Andreas Tobler
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=hoy8j4gjuk.fsf@reger.suse.de \
--to=aj@suse.de \
--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).