From: Michael Matz <matz@suse.de>
To: Richard Guenther <richard.guenther@gmail.com>
Cc: gcc-patches@gcc.gnu.org, Andrew MacLeod <amacleod@redhat.com>,
Andrey Belevantsev <abel@ispras.ru>
Subject: Re: [RFA] expand from SSA form (1/2)
Date: Sun, 26 Apr 2009 21:15:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.0904262311370.29566@wotan.suse.de> (raw)
In-Reply-To: <84fc9c000904261409y289746eax5651fd1006bc3ff2@mail.gmail.com>
Hi,
On Sun, 26 Apr 2009, Richard Guenther wrote:
> > I'd rather remove that field and the fields in the var annotation.
>
> Indeed. I'm testing a patch to remove the aux field.
I had one in testing also removing the value_handle field. It's unused
since some time too (it's moved over to the ssa_name structure directly).
> The partial transition to tuples (the hack going back to GENERIC for
> expansion) also introduced two members, stmt and rn. Fixing that
> partial transition should shrink tree_ann_common_d further.
Yes.
Ciao,
Michael.
next prev parent reply other threads:[~2009-04-26 21:14 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-13 20:50 RFC: " Michael Matz
2009-04-21 18:23 ` Andrew MacLeod
2009-04-22 10:12 ` Paolo Bonzini
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 [this message]
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
2009-04-27 14:15 David Edelsohn
2009-04-27 14:43 ` H.J. Lu
2009-04-27 15:08 ` Michael Matz
2009-04-27 15:11 ` David Edelsohn
2009-04-27 15:51 ` Michael Matz
2009-04-27 17:03 ` David Edelsohn
2009-04-27 17:27 ` David Edelsohn
2009-04-27 19:15 ` David Edelsohn
2009-04-28 0:48 ` Michael Matz
2009-04-28 0:54 ` Luis Machado
2009-04-28 1:22 ` Michael Matz
2009-04-28 13:24 ` Luis Machado
2009-04-30 17:55 ` Luis Machado
2009-05-01 19:33 ` Richard Guenther
2009-05-04 13:38 ` Luis Machado
2009-04-28 16:05 ` David Edelsohn
2009-04-28 16:19 ` Michael Matz
2009-04-28 23:49 ` Michael Matz
2009-04-29 5:50 ` David Edelsohn
2009-04-29 12:48 ` Michael Matz
2009-04-29 13:21 ` David Edelsohn
2009-04-29 13:35 ` Michael Matz
2009-04-29 14:38 ` David Edelsohn
2009-04-29 14:50 ` Richard Guenther
2009-04-29 15:03 ` Andreas Krebbel
2009-04-29 15:11 ` Michael Matz
2009-04-29 15:40 ` Andreas Krebbel
2009-04-29 17:33 ` Michael Matz
2009-04-29 17:41 ` 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=Pine.LNX.4.64.0904262311370.29566@wotan.suse.de \
--to=matz@suse.de \
--cc=abel@ispras.ru \
--cc=amacleod@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.guenther@gmail.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).