public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: lucier@math.purdue.edu To: gcc-gnats@gcc.gnu.org Cc: feeley@iro.umontreal.ca Subject: target/5002: Interesting ICE on sparc-sun-solaris2.8 on "normal" code Date: Mon, 03 Dec 2001 22:36:00 -0000 [thread overview] Message-ID: <20011204063541.22004.qmail@sources.redhat.com> (raw) >Number: 5002 >Category: target >Synopsis: Interesting ICE on sparc-sun-solaris2.8 on "normal" code >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: ice-on-legal-code >Submitter-Id: net >Arrival-Date: Mon Dec 03 22:36:01 PST 2001 >Closed-Date: >Last-Modified: >Originator: B. Lucier >Release: gcc version 3.1 20011203 (experimental) >Organization: >Environment: sparc-sun-solaris2.8, using sun as >Description: This code was hand-written, not machine-generated. For some reason, cc1 ran for over 11 minutes before I killed it when originally running gcc on this file. banach-23% /pkgs/gcc-2.96/lib/gcc-lib/sparc-sun-solaris2.8/3.1/cc1 -m64 -fPIC -O1 -mcpu=ultrasparc -mtune=ultrasparc -fno-math-errno -fno-strict-aliasing -fomit-frame-pointer -fschedule-insns2 -fcall-used-g4 -fcall-used-g5 -fcall-used-g6 -fcall-used-g7 setup.i ___raise_interrupt setup.c: In function `___raise_interrupt': setup.c:96: unrecognizable insn: (insn 13 12 15 (set (reg:DI 110) (lo_sum:DI (reg:DI 110) (unspec:DI[ (symbol_ref:SI ("___gstate")) ] 0))) -1 (insn_list 12 (nil)) (nil)) setup.c:96: Internal compiler error in extract_insn, at recog.c:2128 >How-To-Repeat: run the above command on http://www.math.purdue.edu/~lucier/setup.i.gz >Fix: ??? >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2001-12-04 6:36 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-12-03 22:36 lucier [this message] 2002-04-28 5:15 davem
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=20011204063541.22004.qmail@sources.redhat.com \ --to=lucier@math.purdue.edu \ --cc=feeley@iro.umontreal.ca \ --cc=gcc-gnats@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: linkBe 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).