public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Steve Ellcey <sje@cup.hp.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c/4648: gcc generates bad code at -O2 for SPEC crafty pgm on HPPA 32 HP-UX Date: Mon, 07 Jan 2002 08:56:00 -0000 [thread overview] Message-ID: <20020107165602.29795.qmail@sources.redhat.com> (raw) The following reply was made to PR c/4648; it has been noted by GNATS. From: Steve Ellcey <sje@cup.hp.com> To: rodrigc@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, reva@cup.hp.com, rodrigc@gcc.gnu.org, sje@cup.hp.com, gcc-gnats@gcc.gnu.org Cc: Subject: Re: c/4648: gcc generates bad code at -O2 for SPEC crafty pgm on HPPA 32 HP-UX Date: Mon, 7 Jan 2002 08:50:01 -0800 (PST) > Synopsis: gcc generates bad code at -O2 for SPEC crafty pgm on HPPA 32 HP-UX > > State-Changed-From-To: open->feedback > State-Changed-By: rodrigc > State-Changed-When: Fri Jan 4 21:33:38 2002 > State-Changed-Why: > Is this fixed in the gcc 3.1 tree? > > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=4648 No, it is not fixed in the 3.1 tree. We have a hacked gcc locally that turns off if-conversion and thus avoids the bug but we have no real fix for it. Steve Ellcey sje@cup.hp.com
next reply other threads:[~2002-01-07 16:56 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-01-07 8:56 Steve Ellcey [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-03-30 17:36 Richard Henderson 2002-03-30 17:01 rth 2002-02-17 18:33 rodrigc 2002-01-04 21:33 rodrigc 2001-10-22 17:36 sje
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=20020107165602.29795.qmail@sources.redhat.com \ --to=sje@cup.hp.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: 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).