From: John David Anglin <dave.anglin@bell.net>
To: John David Anglin <dave.anglin@bell.net>
Cc: Torvald Riegel <triegel@redhat.com>,
GNU C Library <libc-alpha@sourceware.org>,
"Carlos O'Donell" <carlos@redhat.com>,
Mike Frysinger <vapier@gentoo.org>, Helge Deller <deller@gmx.de>
Subject: Re: [PATCH] hppa: Use generic pthread conditional variable support
Date: Sun, 12 Mar 2017 20:07:00 -0000 [thread overview]
Message-ID: <3C881958-6859-4E5B-9A81-87834ECCC861@bell.net> (raw)
In-Reply-To: <9A509BCA-658B-494E-B2D4-0D443135E49F@bell.net>
On 2017-03-12, at 4:00 PM, John David Anglin wrote:
> On 2017-03-12, at 3:41 PM, Torvald Riegel wrote:
>
>> Carlos was thinking about re-arranging the struct layout and reserving
>> the LSB of __g1_orig_size for the bit that would be set in a condvar
>> initialized by linuxthreads:
>> https://sourceware.org/ml/libc-alpha/2017-03/msg00058.html
>
> It's up to Carlos. Personally, I'm not sure it's worth maintaining the linuxthreads compatibility.
> Removing it gets rid of a lot of hppa code.
Oh, I know Carlos had said he was going to work on this bug. I sent my patch because Richard asked
if there was any progress on this bug. He's been working on supporting parisc in qemu.
Dave
--
John David Anglin dave.anglin@bell.net
next prev parent reply other threads:[~2017-03-12 20:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-12 14:58 John David Anglin
2017-03-12 17:59 ` Florian Weimer
2017-03-12 18:41 ` John David Anglin
2017-03-12 19:42 ` Torvald Riegel
2017-03-12 20:00 ` John David Anglin
2017-03-12 20:07 ` John David Anglin [this message]
2017-03-15 7:22 ` Mike Frysinger
2017-03-31 21:21 ` Aaro Koskinen
2017-03-31 22:35 ` John David Anglin
2017-04-01 14:01 ` [PATCH v2] hppa: Use generic pthread conditional variable support (BZ #21016) John David Anglin
2017-04-10 23:11 ` [PATCH v3] " John David Anglin
2017-06-04 16:51 ` [PATCH v4] " John David Anglin
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=3C881958-6859-4E5B-9A81-87834ECCC861@bell.net \
--to=dave.anglin@bell.net \
--cc=carlos@redhat.com \
--cc=deller@gmx.de \
--cc=libc-alpha@sourceware.org \
--cc=triegel@redhat.com \
--cc=vapier@gentoo.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).