From: Kevin Klues <klueska@cs.berkeley.edu>
To: Ian Lance Taylor <iant@google.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: TLS, gcc optimizations, and PIC on x86
Date: Thu, 01 Sep 2011 07:15:00 -0000 [thread overview]
Message-ID: <CAJR1fVotbJvjOx-y6iEoobOj_Q+-sjM-cJeFfPk5cDbNf1xDig@mail.gmail.com> (raw)
In-Reply-To: <mcrd3fkonzr.fsf@coign.corp.google.com>
Fair enough. My current solution is adequate for our purposes, as
(like you said) this isn't a very common operation to perform....
That said, do you see any obvious issues with my solution? It seems
to work for all of the test cases I've thrown at it, but I could be
missing something. Additionally, do you have any suggestions for a
better method that achieves similar results? Ideally I'd like a
solution that didn't require the use of the 'optimize' attribute as
(unfortunately) some of the systems on which we'd like to compile our
code still use gcc < 4.4.
Kevin
On Wed, Aug 31, 2011 at 10:00 PM, Ian Lance Taylor <iant@google.com> wrote:
> Kevin Klues <klueska@cs.berkeley.edu> writes:
>
>> Specifically, I want to be able to change the value of my TLS
>> descriptor as well as access TLS variables from that new descriptor
>> within the body of a single function.
>
> As you've discovered, gcc does not support that. It seems like a highly
> unusual feature to want. It would not be hard to change gcc to add an
> option to support this, but I'm not sure it's worth the ongoing
> maintenance cost.
>
> Ian
>
next prev parent reply other threads:[~2011-09-01 7:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-01 1:55 Kevin Klues
2011-09-01 5:01 ` Ian Lance Taylor
2011-09-01 7:15 ` Kevin Klues [this message]
2011-09-06 7:10 ` Ian Lance Taylor
2011-09-06 20:31 ` Kevin Klues
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=CAJR1fVotbJvjOx-y6iEoobOj_Q+-sjM-cJeFfPk5cDbNf1xDig@mail.gmail.com \
--to=klueska@cs.berkeley.edu \
--cc=gcc-help@gcc.gnu.org \
--cc=iant@google.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).