From: Paolo Bonzini <bonzini@gnu.org>
To: Andrew MacLeod <amacleod@redhat.com>
Cc: Michael Matz <matz@suse.de>, gcc-patches@gcc.gnu.org
Subject: Re: RFC: expand from SSA form (1/2)
Date: Wed, 22 Apr 2009 10:12:00 -0000 [thread overview]
Message-ID: <49EEED88.3020900@gnu.org> (raw)
In-Reply-To: <49EE0F0C.1090101@redhat.com>
>> TER is still supported and implemented by deferring expanding an
>> assignment that is TERed to the place where it's actually used.
>> That's a change from before: we don't insert the tree of the RHS
>> directly into the tree that is going to be expanded.
>
> yeah, but TER is basically just a large expression table indexed by ssa
> version. So you just carry that table through to expand and utilize it
> as you encounter the single use during expansion right?
We could use SSA_NAME_VALUE here, maybe?
Paolo
next prev parent reply other threads:[~2009-04-22 10:12 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-13 20:50 Michael Matz
2009-04-21 18:23 ` Andrew MacLeod
2009-04-22 10:12 ` Paolo Bonzini [this message]
2009-04-22 10:16 ` Richard Guenther
2009-04-22 10:54 ` Michael Matz
2009-04-22 11:20 ` Richard Guenther
2009-04-22 12:34 ` Andrew MacLeod
2009-04-22 16:45 ` [RFA] " Michael Matz
2009-04-23 15:10 ` Andrew MacLeod
2009-04-24 9:42 ` Richard Guenther
2009-04-26 20:27 ` Michael Matz
2010-01-19 15:48 ` H.J. Lu
2009-04-24 14:32 ` Richard Guenther
2009-04-24 14:46 ` Richard Guenther
2009-04-26 20:21 ` Michael Matz
2009-04-26 20:34 ` Richard Guenther
2009-04-26 20:53 ` Michael Matz
2009-04-26 21:14 ` Richard Guenther
2009-04-26 21:15 ` Michael Matz
2009-04-26 21:17 ` Richard Guenther
2009-04-26 22:21 ` Michael Matz
2009-04-26 21:42 ` Michael Matz
2009-04-26 22:15 ` Michael Matz
2009-04-27 12:34 ` Michael Matz
2009-04-27 5:47 ` H.J. Lu
2009-04-28 23:49 ` H.J. Lu
2009-04-29 0:21 ` Andrew Pinski
2009-04-30 13:47 ` H.J. Lu
2009-05-29 3:47 ` H.J. Lu
2010-10-20 18:02 ` H.J. Lu
2011-02-14 18:02 ` H.J. Lu
2009-04-27 7:22 ` Hans-Peter Nilsson
2009-04-30 18:18 ` Steve Ellcey
2009-05-01 17:40 ` Michael Matz
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=49EEED88.3020900@gnu.org \
--to=bonzini@gnu.org \
--cc=amacleod@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=matz@suse.de \
/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).