From: Richard Henderson <rth@redhat.com>
To: Aldy Hernandez <aldyh@redhat.com>
Cc: Richard Guenther <richard.guenther@gmail.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 02:54:00 -0000 [thread overview]
Message-ID: <4EB49E46.2090608@redhat.com> (raw)
In-Reply-To: <4EB47B07.7090203@redhat.com>
On 11/04/2011 04:53 PM, Aldy Hernandez wrote:
>> Why is it necessary to know whether a clone is a tm clone?
>
> How do you mean? First, there are a few pretty printing places where we dump that a function is a clone. It is easy to debug dumps when you know which function is the clone and which is the original function, since we will dump both variants at code generation time.
>
> Second, there is code in the TM lowering bits where we assert that we are not trying to lower TM clones ahead of time. And there is a check in gate_tm_init() where we specify that the entire function is a TM region if it is a clone.
>
> etc, etc.
>
> Does this answer your question?
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.
r~
next prev parent reply other threads:[~2011-11-05 2:24 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 [this message]
2011-11-05 9:11 ` Richard Guenther
2011-11-05 18:14 ` Aldy Hernandez
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=4EB49E46.2090608@redhat.com \
--to=rth@redhat.com \
--cc=aldyh@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.guenther@gmail.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).