Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Berlin <dberlin@dberlin.org>
To: Jim Blandy <jimb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFC: initial TLS patch
Date: Tue, 02 Jul 2002 10:08:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.44.0207021303270.19546-100000@dberlin.org> (raw)
In-Reply-To: <npr8imnogv.fsf@zwingli.cygnus.com>

On 2 Jul 2002, Jim Blandy wrote:

> 
> This is a work-in-progress, posted for comments.  This code has never
> been executed, since I only last night got glibc and GCC to actually
> compile and run a program that uses `__thread', and GCC doesn't yet
> emit the Dwarf 2 extension for thread-local variables.

Maybe you could review the patch from april that implements the suggested 
location function mechanism, and use that here to handle thread local 
variable locations, rather than reuse LOC_THREAD_LOCAL_STATIC (Which, 
correct me if i'm wrong, is only currently used by hpread, and pretty 
esay to get rid of before your patch)?
After all, aren't we trying to get rid of all the location types eventually?
It would seem to make sense to not add more uses of them if it can be 
avoided.
Of course, if you have major problems with that patch, it's understandable 
that you'd rather not have this work depend on it, but if it's just minor 
issues, it would seem to make sense to me.


  reply	other threads:[~2002-07-02 17:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-02  8:23 Jim Blandy
2002-07-02 10:08 ` Daniel Berlin [this message]
2002-07-03  2:39 ` Michael Snyder
2002-07-03 13:10   ` Jim Blandy
2002-07-03  8:28 ` Andrew Cagney
2002-07-03 11:30   ` Jim Blandy
2002-07-08 19:19     ` Andrew Cagney
2002-07-08 20:48       ` Jim Blandy
2002-07-08 20:06     ` Andrew Cagney
2002-07-08 20:15       ` Jim Blandy

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=Pine.LNX.4.44.0207021303270.19546-100000@dberlin.org \
    --to=dberlin@dberlin.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jimb@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