From: Torvald Riegel <triegel@redhat.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH] nptl: Document the reason why __kind in pthread_mutex_t is part of the ABI
Date: Mon, 07 Nov 2016 19:21:00 -0000 [thread overview]
Message-ID: <1478546473.7146.875.camel@localhost.localdomain> (raw)
In-Reply-To: <e192eecd-1418-74dc-7f51-55630cafc535@redhat.com>
On Mon, 2016-11-07 at 14:47 +0100, Florian Weimer wrote:
> I started composing a lengthy email about why we should align
> pthread_mutex_t layout on i386 and x86_64 (because cross-process
> compatibility is of more practical importance these days than
> LinuxThreads backwards compatibility). But then I realized that we
> don't have this choice due to the static initializers, which have __kind
> at different offsets.
>
> The attached patch makes this more explicit in the relevant header files.
OK.
prev parent reply other threads:[~2016-11-07 19:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-07 13:47 Florian Weimer
2016-11-07 19:21 ` Torvald Riegel [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=1478546473.7146.875.camel@localhost.localdomain \
--to=triegel@redhat.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@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).