public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hp at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/43853] [4.6 Regression] FAIL: gcc.dg/lto/20090126-1 c_lto_20090126-1_0.o-c_lto_20090126-1_0.o
Date: Thu, 29 Apr 2010 21:16:00 -0000 [thread overview]
Message-ID: <20100429211612.5626.qmail@sourceware.org> (raw)
In-Reply-To: <bug-43853-682@http.gcc.gnu.org/bugzilla/>
------- Comment #1 from hp at gcc dot gnu dot org 2010-04-29 21:16 -------
I'm unsure whether I should tag along on this PR, because the failing range
(last_worked:first_failed) for cris-elf is 158755:158765, which doesn't include
158610. But, I'm doing it anyhow. From gcc-restresults@ it looks like it's
highly host-dependent, but occurring for many targets. My host system is
running Fedora 12, updated about a month ago, gcc-4.4.3-4.fc12.x86_64,
binutils-2.19.51.0.14-37.fc12.x86_64, glibc-2.11.1-1.x86_64. The internal
error message in my gcc.log from r158788 is just (besides the usual ICE
message):
lto1: internal compiler error: Segmentation fault
--
hp at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hp at gcc dot gnu dot org
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
Last reconfirmed|0000-00-00 00:00:00 |2010-04-29 21:16:11
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43853
next prev parent reply other threads:[~2010-04-29 21:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-22 17:25 [Bug middle-end/43853] New: " hjl dot tools at gmail dot com
2010-04-23 12:37 ` [Bug middle-end/43853] " rguenth at gcc dot gnu dot org
2010-04-29 21:16 ` hp at gcc dot gnu dot org [this message]
2010-04-30 8:46 ` hubicka at ucw dot cz
2010-05-12 15:48 ` ro at gcc dot gnu dot org
2010-05-23 13:51 ` howarth at nitro dot med dot uc dot edu
2010-06-01 12:10 ` rguenth at gcc dot gnu dot org
2010-06-01 12:19 ` rguenth at gcc dot gnu dot org
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=20100429211612.5626.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).