public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Ulrich Drepper <drepper@redhat.com>
To: libc-hacker@sources.redhat.com
Subject: Re: gscope + private_futex for alpha
Date: Fri, 25 May 2007 02:26:00 -0000	[thread overview]
Message-ID: <46564931.2080009@redhat.com> (raw)
In-Reply-To: <20070525003502.GA4853@twiddle.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Richard Henderson wrote:
> It seems like much of this same code could be shared with all
> of the targets, particularly those that define TLS_DTV_AT_TP.

Jakub has some patches which I haven't yet looked at.


> +#define lll_futex_wait_flags(futexp, val, flags) \

I don't think this is what I want to do.  The reason is obvious from the
rest of your changes.  Your pthread_once cannot work since the wake call
doesn't use the private flag the same way.  If we'd introduce a new
macro like that we'd have a whole lot of places to inspect and debug.

I'm looking at the generic situation right soon since even x86-64 needs
it for mutexes etc.  What I'll probably end up doing it extend the
existing macros.  This way every usage has to be inspected.

- --
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFGVkkx2ijCOnn/RHQRAjF1AJ9nB9ANs7lbmoJSe0GqaweKjSz4fwCgwXI1
NZeymA0gWKSEHiutmRBry3k=
=Dr09
-----END PGP SIGNATURE-----

  reply	other threads:[~2007-05-25  2:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-25  0:35 Richard Henderson
2007-05-25  2:26 ` Ulrich Drepper [this message]
2007-05-25 17:40   ` Richard Henderson
2007-05-25 17:53     ` Ulrich Drepper

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=46564931.2080009@redhat.com \
    --to=drepper@redhat.com \
    --cc=libc-hacker@sources.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).