public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/24624]  New: [4.1 Regression] internal compiler error: in reload, at reload1.c:1071
Date: Tue, 01 Nov 2005 21:47:00 -0000	[thread overview]
Message-ID: <bug-24624-10053@http.gcc.gnu.org/bugzilla/> (raw)

We ICE compiling the linux kernel.

/usr/lib64/gcc/s390x-suse-linux/4.1.0/cc1 -fpreprocessed inetpeer.i -quiet
-dumpbase inetpeer.c -m64 -mbackchain -msoft-float -march=z900 -mpacked-stack
-mstack-size=8192 -mstack-guard=256 -mwarn-dynamicstack -mwarn-framesize=256
-mzarch -auxbase-strip net/ipv4/.tmp_inetpeer.o -O2 -Wall -Wundef
-Wstrict-prototypes -Wno-trigraphs -Werror-implicit-function-declaration
-Wno-sign-compare -Wdeclaration-after-statement -Wno-pointer-sign -version
-fno-strict-aliasing -fno-common -ffreestanding -fomit-frame-pointer
-finline-limit=10000 -fno-strength-reduce -o inetpeer.s

net/ipv4/inetpeer.c: In function 'peer_check_expire':
net/ipv4/inetpeer.c:461: internal compiler error: in reload, at reload1.c:1071
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://www.suse.de/feedback> for instructions.


-- 
           Summary: [4.1 Regression] internal compiler error: in reload, at
                    reload1.c:1071
           Product: gcc
           Version: 4.1.0
            Status: UNCONFIRMED
          Keywords: ice-on-valid-code
          Severity: critical
          Priority: P3
         Component: target
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: rguenth at gcc dot gnu dot org
GCC target triplet: s390x-*-*


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24624


             reply	other threads:[~2005-11-01 21:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-01 21:47 rguenth at gcc dot gnu dot org [this message]
2005-11-01 21:48 ` [Bug target/24624] " rguenth at gcc dot gnu dot org
2005-11-01 22:49 ` pinskia at gcc dot gnu dot org
2005-11-03  1:28 ` janis at gcc dot gnu dot org
2005-11-03  2:04 ` uweigand at gcc dot gnu dot org
2005-11-03  6:43 ` mmitchel at gcc dot gnu dot org
2005-11-03  6:44 ` mmitchel at gcc dot gnu dot org
2005-11-04  7:56 ` krebbel1 at de dot ibm dot com
2005-11-09 12:01 ` pinskia at gcc dot gnu dot org
2005-11-09 12:02 ` pinskia at gcc dot gnu dot org
2005-11-09 12:18 ` krebbel 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=bug-24624-10053@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).