From: Jakub Jelinek <jakub@redhat.com>
To: Steven Munroe <munroesj@us.ibm.com>
Cc: Ulrich Drepper <drepper@redhat.com>,
GNU libc hacker <libc-hacker@sources.redhat.com>
Subject: Re: [PATCH] clean up PPC for private futex changes.
Date: Tue, 24 Jul 2007 07:11:00 -0000 [thread overview]
Message-ID: <20070724071538.GF4603@sunsite.mff.cuni.cz> (raw)
In-Reply-To: <46A52700.50905@us.ibm.com>
On Mon, Jul 23, 2007 at 05:09:04PM -0500, Steven Munroe wrote:
> But how can header.private_futex be set in the absence of
> __ASSUME_PRIVATE_FUTEX?
header.private_futex is only ever present when
!defined __ASSUME_PRIVATE_FUTEX
and contains either 0 (when private futexes are not supported)
or FUTEX_PRIVATE_FLAG (== 128, when private futexes are supported).
This is not needed when __ASSUME_PRIVATE_FUTEX is defined - we
assume private futexes are supported and thus header.private_futex
would be always 128.
Jakub
prev parent reply other threads:[~2007-07-24 7:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-13 20:44 Steven Munroe
2007-07-23 16:10 ` Ulrich Drepper
2007-07-23 20:43 ` Jakub Jelinek
2007-07-23 22:09 ` Steven Munroe
2007-07-24 7:11 ` Jakub Jelinek [this message]
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=20070724071538.GF4603@sunsite.mff.cuni.cz \
--to=jakub@redhat.com \
--cc=drepper@redhat.com \
--cc=libc-hacker@sources.redhat.com \
--cc=munroesj@us.ibm.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).