mailing list of musl libc
 help / color / mirror / code / Atom feed
From: "A. Wilcox" <AWilcox@Wilcox-Tech.com>
To: James Y Knight <jyknight@google.com>
Cc: musl@lists.openwall.com
Subject: Re: [PATCH v1] string.h: Unconditionally expose C23 functions
Date: Fri, 11 Jul 2025 17:41:47 -0500	[thread overview]
Message-ID: <3561EE5E-CF9F-4AA0-9555-73054822EB75@Wilcox-Tech.com> (raw)
In-Reply-To: <CAA2zVHpDc1wzfcrGWmbvBoCfLfpEC_wBtoUWdRx19cpHA=kGsA@mail.gmail.com>

On Jul 11, 2025, at 15:50, James Y Knight <jyknight@google.com> wrote:
> 
> On Fri, Jul 11, 2025 at 2:55 PM Thorsten Glaser <tg@mirbsd.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

      reply	other threads:[~2025-07-11 22:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-11 13:47 Alejandro Colomar
2025-07-11 16:44 ` [musl] " A. Wilcox
2025-07-11 17:04   ` Rich Felker
2025-07-11 18:55     ` Thorsten Glaser
2025-07-11 20:50       ` James Y Knight
2025-07-11 22:41         ` A. Wilcox [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=3561EE5E-CF9F-4AA0-9555-73054822EB75@Wilcox-Tech.com \
    --to=awilcox@wilcox-tech.com \
    --cc=jyknight@google.com \
    --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).