From: Diego Novillo <dnovillo@redhat.com>
To: Andrew Macleod <amacleod@redhat.com>
Cc: Jan Hubicka <hubicka@ucw.cz>, Jan Hubicka <jh@suse.cz>,
gcc mailing list <gcc@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>,
Richard Henderson <rth@redhat.com>,
stuart@apple.com, dalej@apple.com
Subject: Re: [tree-ssa, RFC] CFG transparent RTL expansion
Date: Wed, 21 Jan 2004 16:12:00 -0000 [thread overview]
Message-ID: <1074701464.20018.24.camel@frodo.toronto.redhat.com> (raw)
In-Reply-To: <1074700677.14945.2487.camel@p4>
On Wed, 2004-01-21 at 10:57, Andrew MacLeod wrote:
> Since I am not offering you a viable alternative, you can take that as a
> removal of my opposition to your plan :-). It may very well turn out to
> have other positive benefits as well. You've clearly thought about it a
> lot more than I have.
>
I also have no major issues with this approach, but we should watch out
for breakage and, particularly, performance regressions. I would very
interested in any benefits we could derive by doing RTL expansion using
a domwalk, for instance.
Diego.
next prev parent reply other threads:[~2004-01-21 16:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-19 5:37 Jan Hubicka
2003-12-19 6:50 ` Andrew MacLeod
2003-12-19 13:14 ` Jan Hubicka
2003-12-19 14:56 ` Jan Hubicka
2003-12-19 18:08 ` Andrew MacLeod
2003-12-19 19:11 ` Jan Hubicka
2003-12-19 19:51 ` Steven Bosscher
2003-12-31 22:57 ` Jan Hubicka
2004-01-20 18:32 ` Jan Hubicka
2004-01-21 15:58 ` Andrew MacLeod
2004-01-21 16:12 ` Diego Novillo [this message]
2004-01-21 18:05 ` Jan Hubicka
2004-01-22 15:07 ` Andrew MacLeod
2004-01-22 15:54 ` Jan Hubicka
2004-01-22 19:33 ` Zdenek Dvorak
2003-12-19 15:01 ` Jan Hubicka
2003-12-19 17:20 ` law
2003-12-19 17:44 ` Jan Hubicka
2003-12-19 18:15 ` Andrew MacLeod
2003-12-19 19:33 ` 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=1074701464.20018.24.camel@frodo.toronto.redhat.com \
--to=dnovillo@redhat.com \
--cc=amacleod@redhat.com \
--cc=dalej@apple.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=jh@suse.cz \
--cc=rth@redhat.com \
--cc=stuart@apple.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).