public inbox for libc-ports@sourceware.org
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos_odonell@mentor.com>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: <libc-ports@sourceware.org>
Subject: Re: Ports updates for NPTL _internal aliases change
Date: Wed, 30 May 2012 13:54:00 -0000	[thread overview]
Message-ID: <4FC61F36.4030005@mentor.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1205300958370.25659@digraph.polyomino.org.uk>

On 5/30/2012 6:00 AM, Joseph S. Myers wrote:
> I've applied these changes to update the ARM and MIPS ports for the move 
> of NPTL to use hidden_def instead of _internal function aliases.
> 
> Other architectures (alpha, ia64, hppa, m68k, tile) will need similar 
> changes.  hppa does more complicated things with _internal function names 
> and I don't know exactly what will be right there.

Yes, for hppa the Linuxthreads->NPTL transition was more difficult, 
and required a wrapper around pthread_cond* functions to manage the 
state of a possibly statically initialized pthread_cond*.

We call the _internal functions from the wrappers after initializing
pthread_cond* variables.

Is that still possible?

Cheers,
Carlos.
-- 
Carlos O'Donell
Mentor Graphics / CodeSourcery
carlos_odonell@mentor.com
carlos@codesourcery.com
+1 (613) 963 1026

  reply	other threads:[~2012-05-30 13:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-30 10:01 Joseph S. Myers
2012-05-30 13:54 ` Carlos O'Donell [this message]
2012-05-30 13:54   ` Joseph S. Myers
2012-05-30 18:23 ` Richard Henderson
2012-05-31  4:29 ` [PATCH] ia64: use hidden_def with internal pthread funcs Mike Frysinger

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=4FC61F36.4030005@mentor.com \
    --to=carlos_odonell@mentor.com \
    --cc=joseph@codesourcery.com \
    --cc=libc-ports@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).