public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/107954] Support -std=c23/gnu23 as aliases of -std=c2x/gnu2x
Date: Fri, 11 Aug 2023 15:48:06 +0000	[thread overview]
Message-ID: <bug-107954-4-f7rVN6Lkgz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107954-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107954

--- Comment #5 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
The straw poll at the June meeting said to keep calling it C23 (votes 
4/12/2 for/against/abstain on the question of changing the informal name 
to C24).  Of course the actual standard will be ISO/IEC 9899:2024 (but 
__STDC_VERSION__ will remain as 202311L, consistent with the informal name 
rather than the publication date, in the absence of a technical DIS 
comment requesting a change of version number being accepted, and 
accepting any technical DIS comments would delay the standard by requiring 
an FDIS).

  parent reply	other threads:[~2023-08-11 15:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-02 19:25 [Bug driver/107954] New: " romain.geissler at amadeus dot com
2022-12-02 21:00 ` [Bug c/107954] " pinskia at gcc dot gnu.org
2022-12-03  8:38 ` lukaszcz18 at wp dot pl
2022-12-07  0:41 ` joseph at codesourcery dot com
2023-08-10 23:07 ` romain.geissler at amadeus dot com
2023-08-11 15:48 ` joseph at codesourcery dot com [this message]
2023-10-19 13:49 ` daniel.lundin.mail at gmail dot com
2023-11-06 15:03 ` cvs-commit at gcc dot gnu.org
2023-11-08  0:25 ` jsm28 at gcc dot gnu.org

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=bug-107954-4-f7rVN6Lkgz@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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. 
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).