public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Matthias Klose <doko@net.local> To: gcc-gnats@gcc.gnu.org, debian-gcc@lists.debian.org Subject: optimization/10315: [3.2/3.3 regression] [powerpc] ICE: in extract_insn, at recog.c:2175 Date: Sat, 05 Apr 2003 13:56:00 -0000 [thread overview] Message-ID: <E191o2c-0006jf-00@tango.net.local> (raw) >Number: 10315 >Category: optimization >Synopsis: [3.2/3.3 regression] [powerpc] ICE: in extract_insn, at recog.c:2175 >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: ice-on-legal-code >Submitter-Id: net >Arrival-Date: Sat Apr 05 13:56:00 UTC 2003 >Closed-Date: >Last-Modified: >Originator: Adam Conrad <adconrad@0c3.net> >Release: 3.2.1 (Debian) (Debian unstable) >Organization: The Debian Project >Environment: System: Debian GNU/Linux (unstable) Architecture: powerpc >Description: [ Reported to the Debian BTS as report #186299. Please CC 186299@bugs.debian.org on replies. Log of report can be found at http://bugs.debian.org/186299 ] Rechecked with 3.2 20030314 and 3.3 20030404. While building php3 on unstable/powerpc, gcc-3.2 ICEs on a file that gcc-2.95 handles fine. Attemps were made with gcc-2.95 (success), gcc-3.2 (fail), and gcc-snapshot (fail). Using -O0 or omitting -fPIC doesn't show the ICE. $ gcc -c -fPIC -O1 pack.i ../functions/pack.c: In function `php3_unpack': ../functions/pack.c:807: error: unrecognizable insn: (insn 1275 1022 3 0 (nil) (set (reg/v:DF 311) (const_double:DF 0.0 [0x0.0p+0])) -1 (nil) (nil)) ../functions/pack.c:807: internal compiler error: in extract_insn, at recog.c:2175 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. [appending the source in a followup] >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2003-04-05 13:56 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-04-05 13:56 Matthias Klose [this message] 2003-04-07 7:16 Steven Bosscher 2003-04-23 3:16 David Edelsohn 2003-04-23 18:26 Geoff Keating 2003-04-23 20:16 David Edelsohn 2003-04-23 22:56 Richard Henderson 2003-04-24 4:56 Richard Henderson 2003-04-25 14:06 David Edelsohn
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=E191o2c-0006jf-00@tango.net.local \ --to=doko@net.local \ --cc=186299@bugs.debian.org \ --cc=debian-gcc@lists.debian.org \ --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).