From: "A. Wilcox" <email@example.com>
Subject: Re: [musl] sem_post() can miss waiters
Date: Mon, 21 Nov 2022 23:41:03 -0600 [thread overview]
Message-ID: <C7419892-0D76-4CC9-9737-1B194FFDCB78@adelielinux.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 726 bytes --]
On Nov 21, 2022, at 6:09 PM, Rich Felker <firstname.lastname@example.org> wrote:
> Regarding your second solution, I think it's more elegant and
> efficient and would be preferable if we were doing this from scratch,
> but changing SEM_VALUE_MAX is arguably an ABI change we should not
With my distro hat on: this isn’t used by too many programs.
Debian Code Search returned a module of Boost. Otherwise, all apps
correctly use sysconf(_SC_SEM_VALUE_MAX) in my cursory glance.
With my gcompat hat on: yes, please don’t change it.
The current value matches glibc and while it doesn’t seem many things
use it, I would hate to have to debug those kind of corner cases in
binary blob code.
[-- Attachment #2: Type: text/html, Size: 4177 bytes --]
next prev parent reply other threads:[~2022-11-22 5:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 5:14 Alexey Izbyshev
2022-11-22 0:09 ` Rich Felker
2022-11-22 5:41 ` A. Wilcox [this message]
2022-11-22 5:41 ` Alexey Izbyshev
2022-12-14 1:48 ` Rich Felker
2022-12-14 10:29 ` Alexey Izbyshev
2023-02-22 18:12 ` Rich Felker
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).