public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rob1weld at aol dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/32024] ICE - libgcc2.c:557: internal compiler error: in fold_checksum_tree, at fold-const.c:12652
Date: Sun, 24 Jun 2007 02:17:00 -0000 [thread overview]
Message-ID: <20070624021725.12605.qmail@sourceware.org> (raw)
In-Reply-To: <bug-32024-13830@http.gcc.gnu.org/bugzilla/>
------- Comment #15 from rob1weld at aol dot com 2007-06-24 02:17 -------
I origonally reported "The bootstrap hardly runs for a few minutes and then I
get an ICE." That is no longer the case. I am making gcc version 4.3.0
20070623.
I'm 4 hours into the make (my build is made using
"--enable-stage1-checking=assert,df,fold,gc,misc,rtl,rtlflag,runtime,tree"), it
is passed all the stages and into the libraries now.
_This_ bug report was marked as "RESOLVED DUPLICATE" of 20623 (which is filed
against 4.1.0 for HTB x86_64-unknown-linux-gnu, while _this_ report is for
4.3.0 HTB i686-pc-linux-gnu - the kind of errors are different too).
Since _this_ report is marked "RESOLVED DUPLICATE" _I_ can not change it to
"RESOLVED FIXED", if someone else who is able would wish to do so that is OK by
me. I do not know that 20623 is fixed and no one has marked it as such.
--
rob1weld at aol dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC|rob1weld at aol dot com |
Known to work| |4.3.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32024
next prev parent reply other threads:[~2007-06-24 2:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-21 15:06 [Bug bootstrap/32024] New: " rob1weld at aol dot com
2007-05-21 15:08 ` [Bug middle-end/32024] " pinskia at gcc dot gnu dot org
2007-05-21 18:09 ` rob1weld at aol dot com
2007-05-21 20:05 ` rob1weld at aol dot com
2007-05-22 2:18 ` rob1weld at aol dot com
2007-05-22 8:53 ` rguenth at gcc dot gnu dot org
2007-05-22 15:02 ` rob1weld at aol dot com
2007-05-24 5:41 ` rob1weld at aol dot com
2007-05-27 22:08 ` rob1weld at aol dot com
2007-05-29 3:57 ` rob1weld at aol dot com
2007-06-20 5:15 ` rob1weld at aol dot com
2007-06-20 8:23 ` [Bug bootstrap/32024] " ubizjak at gmail dot com
2007-06-20 8:55 ` ubizjak at gmail dot com
2007-06-20 8:59 ` ubizjak at gmail dot com
2007-06-20 9:04 ` ubizjak at gmail dot com
2007-06-20 12:28 ` rguenth at gcc dot gnu dot org
2007-06-24 2:17 ` rob1weld at aol dot com [this message]
2007-06-24 12:08 ` rguenth at gcc dot gnu dot org
2007-06-24 12:08 ` rguenth at gcc dot gnu dot org
2007-06-24 17:33 ` rob1weld at aol 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=20070624021725.12605.qmail@sourceware.org \
--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).