mailing list of musl libc
 help / color / mirror / code / Atom feed
From: "Jₑₙₛ Gustedt" <jens.gustedt@inria.fr>
To: musl@lists.openwall.com
Subject: [musl] C23 support, v11
Date: Tue, 19 Mar 2024 15:12:02 +0100	[thread overview]
Message-ID: <20240319151202.6856ebec@inria.fr> (raw)

Hello,
there is now a v.11 of the patches at

      https://forge.icube.unistra.fr/icps/musl/-/branches

The changes are that I tried to rebase such that patches that handle
things from the same standard clause / header are closer together.

One other thing that changed, and that we should perhaps discuss a
bit, is to which version number of `__STDC_VERSION__` we refer. As far
as I can see, gcc and clang have the following strategy for
`-std=c2x`:

 - as long as the compiler support is not complete, the version macro
   has a value that is bigger than `201710L` but smaller than the
   final value `202311L`.

 - when support is considered to be sufficiently complete they switch
   to `202311L`, probably gcc-14 and clang-19

Sufficiently here means that all language features that have no
specific feature tests are implemented. What I see will still be
lacking are `#embed`, `[[reproducible]]` and `[[unsequenced]]`, but
all of these have feature tests.

The first wave of the patches only uses tests for `< 202311L` that is
it supposes all or nothing. Users that use early support compilers for
C23 could fall through the cracks with these. Since both compilers
started early with their C23 support, there are quite a number of
compilers that are concerned, 4 or 5 versions of each, gcc and clang.

On top of this there is patch 592fcd9a that relaxes part of these
tests to just `> 201710L` such that users already get some C23 support
for features that had been implemented early on. Then there are also
patches 8f145eea and 1af530a1

        C23: deal with intermediate C versions for stdbool.h
        C23: deal with intermediate C versions for assert.h

That provide intermediate versions of the corresponding features as
they had been developed over the years.

Jₑₙₛ

-- 
:: ICube :::::::::::::::::::::::::::::: deputy director ::
:: Université de Strasbourg :::::::::::::::::::::: ICPS ::
:: INRIA Nancy Grand Est :::::::::::::::::::::::: Camus ::
:: :::::::::::::::::::::::::::::::::::: ☎ +33 368854536 ::
:: https://icube-icps.unistra.fr/index.php/Jens_Gustedt ::

             reply	other threads:[~2024-03-19 14:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-19 14:12 Jₑₙₛ Gustedt [this message]
2024-04-16  3:57 ` [musl] Re: [PATCH] C23: update some legacy function pointers Michael Forney
2024-04-16 13:42   ` Rich Felker

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=20240319151202.6856ebec@inria.fr \
    --to=jens.gustedt@inria.fr \
    --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).