public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Henderson <rth@redhat.com>
To: IainS <developer@sandoe-acoustics.co.uk>
Cc: Jakub Jelinek <jakub@redhat.com>,
	GCC Patches <gcc-patches@gcc.gnu.org>,
	       Diego Novillo <dnovillo@google.com>,
	Jan Hubicka <hubicka@ucw.cz>
Subject: Re: [Patch, updated] Make emulated TLS lto-friendly.
Date: Thu, 08 Jul 2010 17:10:00 -0000	[thread overview]
Message-ID: <4C36068A.8000600@redhat.com> (raw)
In-Reply-To: <05335B9F-8816-4F2C-BE5F-E2555FBCC0E0@sandoe-acoustics.co.uk>

On 07/08/2010 05:00 AM, IainS wrote:
> On 8 Jul 2010, at 10:34, Jakub Jelinek wrote:
>> with no TLS vars at all, at least it is with non-emulated TLS.
>> Please make sure it doesn't regress for emulated TLS with your patch.
> 
> Well, this wasn't the purpose of the example, O0 is sufficient for that.
> 
> However, it *does* regress on this test, so I've got more work to do there.
> Thanks for catching that.

I very much doubt you'll be able to fix this (minor) regression.

The only reasonable way to prevent that is to *not* lower the TLS
variable so early, so that the optimizers see DECLs where they 
expect to see DECLs.  And that goal appears to be at odds with
making emulated tls LTO friendly.


r~

  reply	other threads:[~2010-07-08 17:10 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 [this message]
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
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=4C36068A.8000600@redhat.com \
    --to=rth@redhat.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 \
    /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).