public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Richard Henderson <rth@redhat.com>
To: rth@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: Sat, 30 Mar 2002 17:36:00 -0000	[thread overview]
Message-ID: <20020331013601.15803.qmail@sources.redhat.com> (raw)

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

From: Richard Henderson <rth@redhat.com>
To: rth@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: Sat, 30 Mar 2002 17:25:45 -0800

 Irritatingly, this is currently "fixed" by CPROP-INSN undoing
 the work performed by PRE earlier.  Almost certainly by
 
 Thu Jan 10 22:35:54 CET 2002  Jan Hubicka  <jh@suse.cz>
 
         * gcse.c (hash_scan_set): Use CONSTANT_INSN_P.
         (cprop_insn): Likewise.
 
 We really need to run a register coelescing pass between the two.
 That's not going to happen for gcc 3.1 though.  In the mean time
 do you mind if I downgrade this to medium priority, since the
 test no longer fails?
 
 
 r~


             reply	other threads:[~2002-03-31  1:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-30 17:36 Richard Henderson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-03-30 17:01 rth
2002-02-17 18:33 rodrigc
2002-01-07  8:56 Steve Ellcey
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=20020331013601.15803.qmail@sources.redhat.com \
    --to=rth@redhat.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=rth@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).