public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: janis187@us.ibm.com To: gcc-gnats@gcc.gnu.org Subject: optimization/5968: flow.c ICE compiling 254.gap on ia64 with -O2 -funroll-loops Date: Thu, 14 Mar 2002 14:26:00 -0000 [thread overview] Message-ID: <20020314222241.8465.qmail@sources.redhat.com> (raw) >Number: 5968 >Category: optimization >Synopsis: flow.c ICE compiling 254.gap on ia64 with -O2 -funroll-loops >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: ice-on-legal-code >Submitter-Id: net >Arrival-Date: Thu Mar 14 14:26:01 PST 2002 >Closed-Date: >Last-Modified: >Originator: Janis Johnson >Release: gcc version 3.1 20020314 (prerelease) >Organization: >Environment: Itanium, Red Hat Linux release 7.1.94 (Roswell) >Description: GCC 3.1 prerelease gets an ICE compiling 254.gap from SPEC CPU2000 with "-O2 -funroll-loops" on ia64-unknown-linux-gnu. Compiler output is: bug.c: In function `f': bug.c:49: Attempt to delete prologue/epilogue insn: (insn 553 551 555 (set (reg:DI 333 ar.lc) (reg:DI 34 r35)) -1 (nil) (nil)) bug.c:49: Internal compiler error in propagate_one_insn, at flow.c:1573 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions. This is a regression from GCC 3.0.4. >How-To-Repeat: Compile the test case on ia64 with -O2 -funroll-loops. >Fix: Unknown >Release-Note: >Audit-Trail: >Unformatted: ----gnatsweb-attachment---- Content-Type: text/plain; name="bug.c" Content-Disposition: inline; filename="bug.c" /* This test case is extracted from file costab.c in 254.gap in SPEC CPU2000. It's been cut down significantly and the names have been changed. The ICE seen when compiling the original file is the same with this version. That ICE occurs with gcc version 3.1 20020314 (prerelease) on ia64-unknown-linux-gnu. From the original file: */ /*************************************************************************** ** *A costab.c GAP source Martin Schoenert *A & Volkmar Felsch ** *Y Copyright 1990-1992, Lehrstuhl D fuer Mathematik, RWTH Aachen, Germany ** **************************************************************************** */ struct S {int i;}; typedef struct S * T; extern T Error (const char *); static long lenw; T f (T hdCall) { T * p1; T * p2; T * p3; long n = 10; long leng; long i, j, k = 3; long gen = 0; if ((long)p3[0] != lenw) return Error( "message 1"); if ((long)p3[k] < 0) for ( i = k; i <= leng; i++) p3[i] = (T)(-(long)p3[i]); for (i = 1; i <= n; i++) if ((long)p1[i] <= -i || (long)p1[i] >= i || (long)p2[i] <= -i || (long)p2[i] >= i ) return Error ("message 2"); return (T)gen; }
next reply other threads:[~2002-03-14 22:26 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-03-14 14:26 janis187 [this message] 2002-03-14 14:46 law 2002-03-14 15:06 Janis Johnson 2002-03-14 19:20 jakub 2002-03-15 5:44 jakub 2002-03-15 11:06 Janis Johnson 2002-03-18 15:38 jakub
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=20020314222241.8465.qmail@sources.redhat.com \ --to=janis187@us.ibm.com \ --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).