linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Edelsohn <dje@watson.ibm.com>
To: Kevin Hendricks <khendricks@ivey.uwo.ca>
Cc: linuxppc-dev@lists.linuxppc.org,
	yellowdog-devel@lists.terrasoftsolutions.com
Subject: Re: Status of 2.5.X kernels on PPC Linux, anyone working with NPTL?
Date: Wed, 09 Oct 2002 12:34:28 -0400	[thread overview]
Message-ID: <200210091634.MAA28260@makai.watson.ibm.com> (raw)
In-Reply-To: Message from Kevin Hendricks <khendricks@ivey.uwo.ca> of "Wed, 09 Oct 2002 11:12:36 EDT." <8B16CEB0-DB99-11D6-BCE2-0030654D6A26@ivey.uwo.ca>


>>>>> Kevin Hendricks writes:

Kevin> Also, is anyone here actively working on Ulrich Drepper's New Posix
Kevin> Thread Library (NPTL) to add in support for ppc Linux?  Has anyone
Kevin> decided on what register will be used for Thread Local Storage on PPC
Kevin> (32bit)?  (Is this r13 on ppc64?).  Have the necessary modifications to
Kevin> the ABI/compiler been made to support a dedicated thread local storage
Kevin> register?

	There still is a question of what the final version of thread
support will look like in Glibc.  TLS support has not been added to
PowerPC GCC yet.  GPR 13 is reserved for the thread ID.  I do not know
whether that also can be used as the TLS base pointer.

David


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2002-10-09 16:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-09 15:12 Status of 2.5.X kernels on PPC Linux, anyone working with NPTL? Kevin Hendricks
2002-10-09 16:34 ` David Edelsohn [this message]
2002-10-09 17:14   ` Kevin Hendricks
2002-11-03 18:28   ` Aldy Hernandez
2002-11-03 18:45     ` Kevin B. Hendricks
2002-11-03 18:55       ` Aldy Hernandez
2002-11-03 20:06         ` Kevin B. Hendricks
2002-10-10  2:26 ` Tom Rini
2002-10-27 12:30 ` Giuliano Pochini

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=200210091634.MAA28260@makai.watson.ibm.com \
    --to=dje@watson.ibm.com \
    --cc=khendricks@ivey.uwo.ca \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=yellowdog-devel@lists.terrasoftsolutions.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 NNTP newsgroup(s).