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/9812: [3.2/3.3 regression] ICE in extract_insn, at recog.c:2148 Date: Sun, 23 Feb 2003 07:16:00 -0000 [thread overview] Message-ID: <E18mqF8-00083k-00@tango.net.local> (raw) >Number: 9812 >Category: optimization >Synopsis: [3.2/3.3 regression] ICE in extract_insn, at recog.c:2148 >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: ice-on-legal-code >Submitter-Id: net >Arrival-Date: Sun Feb 23 07:16:00 UTC 2003 >Closed-Date: >Last-Modified: >Originator: Rick Younie <rick@def.debian.net> >Release: 3.2.2 (Debian) (Debian unstable) >Organization: The Debian Project >Environment: System: Debian GNU/Linux (unstable) Architecture: m68k-linux >Description: [ Reported to the Debian BTS as report #177840. Please CC 177840@bugs.debian.org on replies. Log of report can be found at http://bugs.debian.org/177840 ] This is a regression compared to gcc-3.0.4 and gcc-2.95.[34]. The following code, extracted from gtk+2.0 ICEs on m68k-linux, reducing to -O1 avoids the ICE. Checked with 3.2 branch 20021231 and 3.3 branch 20030221 $ gcc-3.2 -O2 -pthread -g -Wall -fPIC -c bug-177840-3.i bug-177840-3.i: In function `bilinear_quadrant': bug-177840-3.i:55: unrecognizable insn: (insn 263 69 71 (set (reg:DF 17 %fp1) (const_double:DF 0 [0x0] 0 [0x0] 0 [0x0])) -1 (nil) (nil)) bug-177840-3.i:55: Internal compiler error in extract_insn, at recog.c:2148 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions. $ /scratch/gcc/gcc-snapshot-20030221/build/gcc/xgcc -B/scratch/gcc/gcc-snapshot-20030221/build/gcc/ -O2 -pthread -g -Wall -fPIC -c bug-177840-3.i bug-177840-3.i: In function `bilinear_quadrant': bug-177840-3.i:55: error: unrecognizable insn: (insn 256 67 68 6 (nil) (set (reg:DF 16 %fp0) (const_double:DF 0 [0x0] 0.0 [0x0.0p+0])) -1 (nil) (nil)) bug-177840-3.i:55: internal compiler error: in extract_insn, at recog.c:2175 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions. ------------------------------------------- double bilinear_quadrant (double bx0, double bx1, double by0, double by1) { double ax0, ax1, ay0, ay1; double x0, x1, y0, y1; ax0 = 0.; ax1 = 1.; ay0 = 0.; ay1 = 1.; if (ax0 < bx0) { if (ax1 > bx0) { x0 = bx0; x1 = (((ax1) < (bx1)) ? (ax1) : (bx1)); } else return 0; } else { if (bx1 > ax0) { x0 = ax0; x1 = (((ax1) < (bx1)) ? (ax1) : (bx1)); } else return 0; } if (ay0 < by0) { if (ay1 > by0) { y0 = by0; y1 = (((ay1) < (by1)) ? (ay1) : (by1)); } else return 0; } else { if (by1 > ay0) { y0 = ay0; y1 = (((ay1) < (by1)) ? (ay1) : (by1)); } else return 0; } return 0.25 * (x1*x1 - x0*x0) * (y1*y1 - y0*y0); } ------------------------------------------- >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2003-02-23 7:16 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=E18mqF8-00083k-00@tango.net.local \ --to=doko@net.local \ --cc=177840@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).