public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Janis Johnson <janis187@us.ibm.com> To: jakub@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: Fri, 15 Mar 2002 11:06:00 -0000 [thread overview] Message-ID: <20020315190602.21433.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: jakub@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, janis187@us.ibm.com, gcc-gnats@gcc.gnu.org Cc: Subject: Re: optimization/5968: flow.c ICE compiling 254.gap on ia64 with -O2 -funroll-loops Date: Fri, 15 Mar 2002 11:00:58 -0800 On Fri, Mar 15, 2002 at 01:44:31PM -0000, jakub@gcc.gnu.org wrote: > Synopsis: flow.c ICE compiling 254.gap on ia64 with -O2 -funroll-loops > > State-Changed-From-To: open->feedback > State-Changed-By: jakub > State-Changed-When: Fri Mar 15 05:44:30 2002 > State-Changed-Why: > Are you sure you had my patch installed? > Cannot reproduce it today at all and it really looks > like 5891. > > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5968 OK, I'm embarrassed. I updated my 3.1 tree yesterday and built and ran 200.sixtrack and 254.gap; 200.sixtrack built and ran fine, so I assumed that I had picked up Jakub's patch, but it turns out I didn't. Today I updated the tree again, verified that his patch is there, and both tests work fine. Sorry for the confusion, PR 5968 is the same as PR 5891. I also saw runtime failures with 254.gap on i686-pc-linux.gnu, and with Jakub's fix for 5891 it now works fine. I plan to continue building and running (with the small test input) SPEC CPU2000 benchmarks with a variety of optimization options and tracking down and reporting failures. Janis
next reply other threads:[~2002-03-15 19:06 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-03-15 11:06 Janis Johnson [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-03-18 15:38 jakub 2002-03-15 5:44 jakub 2002-03-14 19:20 jakub 2002-03-14 15:06 Janis Johnson 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=20020315190602.21433.qmail@sources.redhat.com \ --to=janis187@us.ibm.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=jakub@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).