Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <3561EE5E-CF9F-4AA0-9555-73054822EB75@Wilcox-Tech.com>
Date: Fri, 11 Jul 2025 17:41:47 -0500
From: "A. Wilcox" <AWilcox@...cox-Tech.com>
To: James Y Knight <jyknight@...gle.com>
Cc: musl@...ts.openwall.com
Subject: Re: [PATCH v1] string.h: Unconditionally expose C23 functions

On Jul 11, 2025, at 15:50, James Y Knight <jyknight@...gle.com> wrote:
> 
> On Fri, Jul 11, 2025 at 2:55 PM Thorsten Glaser <tg@...bsd.de> wrote:
> > I’d ask to at least
> > consider it a little longer given you have actual user reports
> > that they have to patch out things like this downstream.
> 
> Do you have examples of what, concretely, was broken and required the patch? The commit message for the change that ifdef'd away aligned_alloc, at_quick_exit, and quick_exit provides no info about why you found it important to patch downstream -- only that you did so.

NSS, cURL, Boost, and multiple Perl pods all define their own `quick_exit` methods or variables.  Debian Code Search may find more; this is just what I have local in /usr/src.

It is also a hard-fail from PCTS (the POSIX Conformance Test Suite) for an implementation to have visible definitions in the main namespace that are not defined by the standard.

It also ensures that -std is specified properly by upstream packages.  We have already reported multiple instances to upstreams of their not specifying the correct standard version in their build recipes, causing spurious failures.  I can find some of these reports if you need them.

Best,
-Anna

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.