From: Rich Felker <dalias@libc.org>
To: Ed Maste <emaste@freebsd.org>
Cc: musl@lists.openwall.com
Subject: Re: qsort_r or qsort_s in musl
Date: Mon, 10 Sep 2018 13:43:28 -0400 [thread overview]
Message-ID: <20180910174328.GS1878@brightrain.aerifal.cx> (raw)
In-Reply-To: <CAPyFy2CHOSetvJKBL0Re++rSTVJYRnTB27Zsph8_xharyTHGww@mail.gmail.com>
On Mon, Sep 10, 2018 at 01:27:00PM -0400, Ed Maste wrote:
> > qsort_r was at first rejected because of the conflicting definitions
> > -- existence of same-named interfaces with different semantics or
> > signatures is one of the big criteria for exclusion of nonstandard
> > extensions in musl. However, from the FreeBSD side at least there
> > seems to be interest in dropping their version and agreeing upon a
> > standard aligned with glibc's version, for the sake of POSIX:
>
> If you want to see the current state of this in FreeBSD, we have a
> code review in progress in Phabricator at
> https://reviews.freebsd.org/D17083. If POSIX standardizes on the glibc
> version I'm sure we'll follow.
Thanks for the update. It looks like we have a sort of 3- (N-?) way
deadlock:
A: POSIX adopts qsort_r with glibc signature
B: FreeBSD switches qsort_r to glibc signature
C: musl adds qsort_r with glibc signature
A seems kinda stalled and dependent on B and possibly others.
B seems dependent on A.
C seems dependent on A || B || some approximation of A. ;-)
Fortunately it looks like we're all on the same page about where it
should end up and all sides still want it to happen.
Rich
prev parent reply other threads:[~2018-09-10 17:43 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
2018-09-10 17:27 ` Ed Maste
2018-09-10 17:43 ` Rich Felker [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=20180910174328.GS1878@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=emaste@freebsd.org \
--cc=musl@lists.openwall.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).