From: "A. Wilcox" <awilfox@adelielinux.org>
To: musl@lists.openwall.com
Subject: Re: [musl] [PATCH] add support for pthread_sigqueue
Date: Wed, 5 Feb 2020 17:06:11 -0600 [thread overview]
Message-ID: <7c6d2ddc-99ba-4f82-c1dc-5114e7b8f69e@adelielinux.org> (raw)
In-Reply-To: <20200205192756.GC1663@brightrain.aerifal.cx>
[-- Attachment #1.1: Type: text/plain, Size: 1058 bytes --]
On 05/02/2020 13:27, Rich Felker wrote:
> Is the naming pthread_sigqueue (vs pthread_sigqueue_np) intentional?
> Normally pthread functions that are not part of the standard are
> introduced as _np (non-portable) and promoted later if accepted as
> standards since the pthread_* namespace is reserved for future
> directions of the standard. Does glibc have this function with the
> same signature already?
The signature differs only with the constness of the third argument in
the header. (The constness in the function implementation is correct.)
It is implemented not only in glibc, but additionally in Solaris 11:
https://docs.oracle.com/cd/E88353_01/html/E37843/pthread-sigqueue-3c.html
The corresponding system call was added in Linux 2.6.31, if it matters.
I have no comments (positive or negative) regarding the addition of this
call nor its implementation other than that the constness should be
fixed in the header.
Best,
--arw
--
A. Wilcox (awilfox)
Project Lead, Adélie Linux
https://www.adelielinux.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-02-05 23:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 14:12 Daniel Fahlgren
2020-02-05 19:27 ` Rich Felker
2020-02-05 23:06 ` A. Wilcox [this message]
2020-02-06 0:17 ` Rich Felker
2020-02-06 1:12 ` A. Wilcox
2020-02-05 23:08 ` Daniel Fahlgren
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=7c6d2ddc-99ba-4f82-c1dc-5114e7b8f69e@adelielinux.org \
--to=awilfox@adelielinux.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).