public inbox for
 help / color / mirror / Atom feed
From: Florian Weimer <>
To: Joseph Myers <>
Subject: Re: Refer to C23 in place of C2X in glibc
Date: Thu, 01 Feb 2024 08:58:12 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <> (Joseph Myers's message of "Wed, 31 Jan 2024 19:00:13 +0000 (UTC)")

* Joseph Myers:

> WG14 decided to use the name C23 as the informal name of the next
> revision of the C standard (notwithstanding the publication date in
> 2024).  Update references to C2X in glibc to use the C23 name.
> This is intended to update everything *except* where it involves
> renaming files (the changes involving renaming tests are intended to
> be done separately).  In the case of the _ISOC2X_SOURCE feature test
> macro - the only user-visible interface involved - support for that
> macro is kept for backwards compatibility, while adding
> Tested for x86_64.
> diff --git a/NEWS b/NEWS
> index 39a55f5767..2d8eaffc58 100644
> --- a/NEWS
> +++ b/NEWS
> @@ -14,6 +14,13 @@ Major new features:
>    in order to support unsigned __int128 and/or unsigned _BitInt(N) operands
>    with arbitrary precisions when supported by the target.
> +* The GNU C Library now supports a feature test macro _ISOC23_SOURCE to
> +  enable features from the ISO C23 standard.  Only some features from
> +  this standard are supported by the GNU C Library.  The older name
> +  _ISOC2X_SOURCE is still supported.  Features from C23 are also enabled
> +  by _GNU_SOURCE, or by compiling with the GCC options -std=c23,
> +  -std=gnu23, -std=c2x or -std=gnu2x.
> +
>  Deprecated and removed features, and other changes affecting compatibility:

Looks okay.

Reviewed-by: Florian Weimer <>


      reply	other threads:[~2024-02-01  7:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-31 19:00 Joseph Myers
2024-02-01  7:58 ` Florian Weimer [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:

* 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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).