public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jan Hubicka <jh@suse.cz>
To: Richard Henderson <rth@redhat.com>, Jan Hubicka <jh@suse.cz>,
	gcc-patches@gcc.gnu.org
Subject: Re: ifcvt pass ordering
Date: Fri, 25 Oct 2002 14:12:00 -0000	[thread overview]
Message-ID: <20021025211243.GG28282@kam.mff.cuni.cz> (raw)
In-Reply-To: <20021025211025.GD7572@redhat.com>

> > ... but that is something I would like to handle
> > separately from this simple patch.
> 
> So what does this accomplish that the call during cse2 does not?
The ifcvt pass even without liveness does quite a lot, but once tracing
is done it does almost nothing.  So by reordering ifcvt before cse2 and
tracer results in quite a bit better code (that can be futher improved
if liveness were available before first ifcvt pass)

Honza
> 
> 
> r~

  reply	other threads:[~2002-10-25 21:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-16 11:24 Jan Hubicka
2002-10-25 13:57 ` Richard Henderson
2002-10-25 14:07   ` Jan Hubicka
2002-10-25 14:10     ` Richard Henderson
2002-10-25 14:12       ` Jan Hubicka [this message]
2002-10-25 14:19         ` Richard Henderson
2002-10-25 14:27           ` Jan Hubicka
2002-10-25 15:02             ` Richard Henderson
2002-10-26 10:27               ` Graham Stott
2002-10-26 14:57 ` Geoff Keating
2002-10-26 15:02   ` Jan Hubicka
2002-10-26 15:25   ` Fix for " Jan Hubicka
2002-10-29  6:30     ` Richard Henderson
2002-12-10 12:30 ` Eric Botcazou
2002-11-02 19:52 John David Anglin
2002-11-03  3:30 ` Jan Hubicka
2002-11-03  9:38   ` John David Anglin
2003-01-15 22:44   ` John David Anglin
2003-03-06 16:05 ` Jan Hubicka

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=20021025211243.GG28282@kam.mff.cuni.cz \
    --to=jh@suse.cz \
    --cc=gcc-patches@gcc.gnu.org \
    --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).