From: Aldy Hernandez <aldyh@redhat.com>
To: Richard Guenther <richard.guenther@gmail.com>
Cc: Richard Henderson <rth@redhat.com>,
gcc-patches <gcc-patches@gcc.gnu.org>,
Torvald Riegel <triegel@redhat.com>
Subject: Re: [patch] 19/n: trans-mem: compiler tree/gimple stuff
Date: Sat, 05 Nov 2011 18:14:00 -0000 [thread overview]
Message-ID: <4EB551BE.9050600@redhat.com> (raw)
In-Reply-To: <CAFiYyc2HfXtPYMwrnTu-5Lt2A-MqV6HNAGR0Z86dj=EH345oug@mail.gmail.com>
>> Richi, if it's the use of the bit in the tree node that you're worried about,
>> we could probably put it in cgraph_node.local instead. But we do need the
>> knowledge.
>
> Yeah, I was worried about /* 1 bit left */ ;) Putting it in the
> cgraph node sounds more appealing
> indeed.
Richi, is this a blocker, or merely a suggestion? If this is a
requirement for merging, I can do so. Just want to make sure where best
to spend my time.
If this is a suggestion, I can put it on my laundry list of future
things todo (after merge, 4.8?, etc).
next prev parent reply other threads:[~2011-11-05 15:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-03 19:40 Aldy Hernandez
2011-11-04 10:44 ` Richard Guenther
2011-11-05 0:25 ` Aldy Hernandez
2011-11-05 2:54 ` Richard Henderson
2011-11-05 9:11 ` Richard Guenther
2011-11-05 18:14 ` Aldy Hernandez [this message]
2011-11-05 23:03 ` Richard Guenther
2011-11-06 10:10 ` Aldy Hernandez
2011-11-06 10:51 ` Richard Guenther
2011-11-05 3:11 ` Richard Henderson
2011-11-05 3:23 ` Richard Henderson
2011-11-05 10:18 ` Richard Guenther
2011-11-05 21:26 ` Aldy Hernandez
2011-11-05 23:16 ` Richard Guenther
2011-11-07 19:06 ` Richard Henderson
2011-11-07 19:46 ` Aldy Hernandez
2011-11-07 22:38 ` Richard Guenther
2011-11-06 0:51 ` Aldy Hernandez
2011-11-06 10:17 ` Richard Guenther
2011-11-07 17:47 ` Richard Henderson
2011-11-04 15:40 ` Michael Matz
2011-11-05 8:47 ` Aldy Hernandez
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=4EB551BE.9050600@redhat.com \
--to=aldyh@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.guenther@gmail.com \
--cc=rth@redhat.com \
--cc=triegel@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).