From: Rich Felker <dalias@libc.org>
To: Leah Neukirchen <leah@vuxu.org>
Cc: Eric Blake <eblake@redhat.com>,
musl@lists.openwall.com, Balazs Kezes <rlblaster@gmail.com>
Subject: Re: Re: qsort_r or qsort_s in musl
Date: Tue, 4 Sep 2018 12:13:34 -0400 [thread overview]
Message-ID: <20180904161334.GD1878@brightrain.aerifal.cx> (raw)
In-Reply-To: <87lg8h8dw1.fsf@vuxu.org>
On Tue, Sep 04, 2018 at 05:45:50PM +0200, Leah Neukirchen wrote:
> Rich Felker <dalias@libc.org> writes:
>
> > Thanks. Final acceptance into POSIX isn't completely mandatory for us
> > to adopt it, but I'd at least want to see that FreeBSD (others would
> > be great too) is moving forward with converting over to the
> > glibc/proposed-POSIX signature so the risk of this devolving into a
> > deadlock is in the past.
>
> AFAICS, macOS and DragonFlyBSD also use the FreeBSD signature.
> OpenBSD never implemented qsort_r; NetBSD proposed to implemement the
> glibc signature in 2013, but this didn't seem to be merged.
Yes, I'm aware there are a couple others and at least one (OSX) is
probably going to be hard to get to change. I'm pretty okay with that
as long as there is good consensus among the implementations that
actually care about portability and consensus. OSX has so many serious
conformance bugs, and is stuck so far in the past (17 years -- POSIX
2001, with problems even conforming to that), that it's like MSVCRT;
they really don't have standing to push their way on this.
Rich
next prev parent reply other threads:[~2018-09-04 16:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-03 20:57 Balazs Kezes
2018-09-03 22:53 ` Rich Felker
2018-09-04 7:41 ` Balazs Kezes
2018-09-04 14:48 ` Eric Blake
2018-09-04 15:18 ` Rich Felker
2018-09-04 15:45 ` Balazs Kezes
2018-09-04 15:45 ` Leah Neukirchen
2018-09-04 16:13 ` Rich Felker [this message]
2018-09-10 17:27 ` Ed Maste
2018-09-10 17:43 ` Rich Felker
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=20180904161334.GD1878@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=eblake@redhat.com \
--cc=leah@vuxu.org \
--cc=musl@lists.openwall.com \
--cc=rlblaster@gmail.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).