public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Toon Moene <toon@moene.indiv.nluug.nl>
To: Jan Hubicka <jh@suse.cz>
Cc: Richard Henderson <rth@redhat.com>, gcc-patches@gcc.gnu.org
Subject: Re: cprop "fix"
Date: Thu, 18 Jul 2002 12:57:00 -0000	[thread overview]
Message-ID: <3D371DD3.B61EA34C@moene.indiv.nluug.nl> (raw)
In-Reply-To: <20020718195351.GA10794@atrey.karlin.mff.cuni.cz>

Jan Hubicka wrote:

> It does basically same as 386 version - slightly more PRE improvements
> as PRE does not have to work around parallels as i386 compiler does.
> 
> I can't benchmark, as the machine is busy by something else :)
> But the patch has passed full bootstrap and regtesting on that machine
> as well, so hope the try_replace_reg works as supposed to now.

Hmmm, yes, thanks, but are you going to commit the stuff, or am I better
off just aplying it to the current trunk and see what it buys us ?

Thanks in advance,

-- 
Toon Moene - mailto:toon@moene.indiv.nluug.nl - phoneto: +31 346 214290
Saturnushof 14, 3738 XG  Maartensdijk, The Netherlands
Maintainer, GNU Fortran 77: http://gcc.gnu.org/onlinedocs/g77_news.html
Join GNU Fortran 95: http://g95.sourceforge.net/ (under construction)

  reply	other threads:[~2002-07-18 19:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-13 12:00 Jan Hubicka
2002-07-15  4:37 ` Jan Hubicka
2002-07-15  4:50   ` Paolo Carlini
2002-07-17  9:18 ` Richard Henderson
2002-07-17  9:34   ` Jan Hubicka
2002-07-17  9:42     ` Jan Hubicka
2002-07-17 10:52       ` Richard Henderson
2002-07-18  0:46         ` Jan Hubicka
2002-07-18  3:21           ` Jan Hubicka
2002-07-18 12:18             ` Toon Moene
2002-07-18 12:57               ` Jan Hubicka
2002-07-18 12:57                 ` Toon Moene [this message]
2002-07-18 13:06                   ` Jan Hubicka
2002-07-19 12:16 ` Richard Henderson
2002-07-29 12:23 John David Anglin

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=3D371DD3.B61EA34C@moene.indiv.nluug.nl \
    --to=toon@moene.indiv.nluug.nl \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jh@suse.cz \
    --cc=rth@redhat.com \
    /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).