Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Jun Sun <jsun@mvista.com>
To: Daniel Jacobowitz <dan@debian.org>
Cc: Dominic Sweetman <dom@mips.com>,
	linux-mips@linux-mips.org, jsun@mvista.com
Subject: Re: anybody tried NPTL?
Date: Mon, 23 Aug 2004 10:37:31 -0700	[thread overview]
Message-ID: <20040823173731.GC23004@mvista.com> (raw)
In-Reply-To: <20040823132853.GA31354@nevyn.them.org>

On Mon, Aug 23, 2004 at 09:28:53AM -0400, Daniel Jacobowitz wrote:
> On Fri, Aug 20, 2004 at 02:46:11PM +0100, Dominic Sweetman wrote:
> > I guess our main message was that we felt it would be a mistake just
> > to add a thread register to o32 (which produces a substantially
> > incompatible new ABI anyway).
> 
> Completely agree...
> 
> > Until that all works, what we had in mind is that we'd do NPTL over
> > o32 by defining a system call to return a per-thread ID which is or
> > can be converted into a per-thread data pointer.  We suspected that
> > NPTL's per-thread-data model allows the use of cunning macros or
> > library functions to make that look OK.
> > 
> > Ought we to go further and see exactly how that can be done?
> 
> It shouldn't be at all hard.  The way NPTL's __thread support works,
> the only things that should have to know where the TLS base is are
> (A) GCC, so it can load it and (B) GDB, via some new ptrace op. 

Are you implying one can implement TLS support without changing O32
ABI?  Interesting...

I know Boris Hu has tried to implemented NPTL with another approach which
does not rely on TLS support (use "--without-tls").  According to him
this approach is getting harder these days.

Jun

  parent reply	other threads:[~2004-08-23 17:37 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-04 22:29 anybody tried NPTL? Jun Sun
2004-08-05  1:08 ` Kumba
2004-08-05 17:14   ` Jun Sun
2004-08-06  2:03   ` Ralf Baechle
2004-08-19 14:17 ` Dominic Sweetman
2004-08-19 14:31   ` Alec Voropay
2004-08-19 14:31     ` Alec Voropay
2004-08-20  6:07     ` Dominic Sweetman
2004-08-20  6:07       ` Dominic Sweetman
2004-08-23 12:28     ` Ralf Baechle
2004-08-23 15:09       ` Alec Voropay
2004-08-23 15:09         ` Alec Voropay
2004-08-23 17:19         ` Ralf Baechle
2004-08-19 16:01   ` David Daney
2004-08-20  6:19     ` Dominic Sweetman
2004-08-19 22:16   ` Jun Sun
2004-08-20 13:46     ` Dominic Sweetman
2004-08-23 13:28       ` Daniel Jacobowitz
2004-08-23 17:12         ` Ralf Baechle
2004-08-23 17:44           ` Daniel Jacobowitz
2004-08-23 19:13             ` Ralf Baechle
2004-08-23 17:37         ` Jun Sun [this message]
2004-08-23 19:25           ` Ralf Baechle
2004-08-20 13:12   ` Thiemo Seufer
2004-08-20 16:52     ` Dominic Sweetman
2004-09-01  9:17   ` Richard Sandiford

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=20040823173731.GC23004@mvista.com \
    --to=jsun@mvista.com \
    --cc=dan@debian.org \
    --cc=dom@mips.com \
    --cc=linux-mips@linux-mips.org \
    /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