From: "Andrew Pinski" <pinskia@gmail.com>
To: "Richard Guenther" <rguenther@suse.de>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Shrink tree_block
Date: Sat, 24 Nov 2007 23:33:00 -0000 [thread overview]
Message-ID: <de8d50360711241050m7361e5eag911477c6282572d4@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0711241951161.4148@zhemvz.fhfr.qr>
On 11/24/07, Richard Guenther <rguenther@suse.de> wrote:
> This shrinks tree_block by noting that with mapped location the
> block locus now pairs with the flags. Also blocks do not need
> a type and access to the chain member of tree_common is conveniently
> wrapped with BLOCK_CHAIN.
>
> So, bootstrapped and tested on x86_64-unknown-linux-gnu, I'll apply
> this as a memory-savings regression fix later.
This is not complete, you need to have BLOCK return true for GIMPLE_TUPLE_P.
And you should have GENERIC_NEXT for BLOCKs return BLOCK_CHAIN.
Thanks,
Andrew Pinski
next prev parent reply other threads:[~2007-11-24 18:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-24 23:31 Richard Guenther
2007-11-24 23:33 ` Andrew Pinski [this message]
2007-11-25 19:18 ` Richard Guenther
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=de8d50360711241050m7361e5eag911477c6282572d4@mail.gmail.com \
--to=pinskia@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=rguenther@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).