From: Richard Guenther <richard.guenther@gmail.com>
To: Richard Henderson <rth@redhat.com>
Cc: IainS <developer@sandoe-acoustics.co.uk>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Diego Novillo <dnovillo@google.com>,
Jan Hubicka <hubicka@ucw.cz>, Jakub Jelinek <jakub@redhat.com>
Subject: Re: [Patch, updated] Make emulated TLS lto-friendly.
Date: Thu, 08 Jul 2010 09:25:00 -0000 [thread overview]
Message-ID: <AANLkTik3sOZ6Uo346vHzJlu_66aMV9tb1gnBxjHemQ-n@mail.gmail.com> (raw)
In-Reply-To: <4C350C25.2030308@redhat.com>
On Thu, Jul 8, 2010 at 1:22 AM, Richard Henderson <rth@redhat.com> wrote:
> Finally, as a follow-up, I think the alias oracle needs to be taught what
> __builtin_emutls_get_address does. Namely, return the address of the
> associated TLS variable. This is the only way I can think of to avoid
> the optimization penalty that you're introducing because of exposing the
> control variable and the function call at this point.
While teaching the oracle about __builtin_emutls_get_address will
help disambiguating against emutls accesses it will not be enough
to trigger CSE. So it would be nice to have a testcase that shows
we can properly CSE emutls accesses in FRE (in theory it shuld
work as __builtin_emutls_get_address is const).
Richard.
>
>
> r~
>
next prev parent reply other threads:[~2010-07-08 9:25 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-03 14:11 IainS
2010-07-07 23:22 ` Richard Henderson
2010-07-08 8:42 ` IainS
2010-07-08 9:32 ` Jakub Jelinek
2010-07-08 12:01 ` IainS
2010-07-08 17:10 ` Richard Henderson
2010-07-08 17:21 ` Jan Hubicka
2010-07-08 17:34 ` Richard Henderson
2010-07-08 16:14 ` Richard Henderson
2010-07-08 16:21 ` IainS
2010-07-08 17:04 ` Richard Henderson
2010-07-08 9:25 ` Richard Guenther [this message]
2010-07-08 11:59 ` [Patch, testsuite] " IainS
2010-07-08 12:05 ` IainS
2010-07-08 19:07 ` IainS
2010-07-08 19:19 ` Richard Henderson
2010-07-09 12:11 ` IainS
2010-07-12 14:48 ` Jack Howarth
2010-07-12 15:18 ` Richard Henderson
2010-07-12 17:04 ` Richard Henderson
2010-07-12 20:08 ` Richard Henderson
2010-07-13 15:47 ` Richard Henderson
2010-07-13 18:56 ` Richard Henderson
2010-07-13 20:01 ` Richard Henderson
2010-07-13 20:04 ` Nathan Froyd
2010-07-13 21:20 ` Richard Henderson
2010-07-13 21:23 ` Nathan Froyd
2010-07-13 20:46 ` Richard Guenther
2010-07-13 21:19 ` Richard Henderson
2010-07-13 21:39 ` Andrew Pinski
2010-07-13 21:48 ` Richard Henderson
2010-07-14 8:26 ` Richard Guenther
2010-07-14 16:00 ` Richard Henderson
2010-07-14 16:25 ` Richard Guenther
2010-07-14 8:11 ` 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=AANLkTik3sOZ6Uo346vHzJlu_66aMV9tb1gnBxjHemQ-n@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=developer@sandoe-acoustics.co.uk \
--cc=dnovillo@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=jakub@redhat.com \
--cc=rth@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).