public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Janis Johnson <janis187@us.ibm.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: optimization/5968: flow.c ICE compiling 254.gap on ia64 with -O2 -funroll-loops
Date: Thu, 14 Mar 2002 15:06:00 -0000	[thread overview]
Message-ID: <20020314230602.20256.qmail@sources.redhat.com> (raw)

The following reply was made to PR optimization/5968; it has been noted by GNATS.

From: Janis Johnson <janis187@us.ibm.com>
To: law@redhat.com
Cc: janis187@us.ibm.com, gcc-gnats@gcc.gnu.org
Subject: Re: optimization/5968: flow.c ICE compiling 254.gap on ia64 with -O2 -funroll-loops
Date: Thu, 14 Mar 2002 15:00:52 -0800

 On Thu, Mar 14, 2002 at 03:44:08PM -0700, law@redhat.com wrote:
 > In message <20020314222241.8465.qmail@sources.redhat.com>, janis187@us.ibm.com 
 > writes:
 >  > 
 >  > >Number:         5968
 >  > >Category:       optimization
 >  > >Synopsis:       flow.c ICE compiling 254.gap on ia64 with -O2 -funroll-loop
 >  > s
 >  > >Class:          ice-on-legal-code
 >  > >Submitter-Id:   net
 >  > >Arrival-Date:   Thu Mar 14 14:26:01 PST 2002
 >  > >Release:        gcc version 3.1 20020314 (prerelease)
 >  > >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
 > There's a reasonable chance this patch from Jakub will fix your problem.
 > It was approved by Richard this afternoon.
 > 
 > > 	PR optimization/5891
 > > 	* unroll.c (copy_loop_body) [CALL_INSN]: Copy SIBLING_CALL_P flag.
 
 I should have mentioned in the PR that although this appears to be the
 same as the bug described in PR 5891, it occurs even with Jakub's fix
 for 5891.
 
 Janis


             reply	other threads:[~2002-03-14 23:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-14 15:06 Janis Johnson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-03-18 15:38 jakub
2002-03-15 11:06 Janis Johnson
2002-03-15  5:44 jakub
2002-03-14 19:20 jakub
2002-03-14 14:46 law
2002-03-14 14:26 janis187

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=20020314230602.20256.qmail@sources.redhat.com \
    --to=janis187@us.ibm.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).