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: Wed, 07 Dec 2022 00:41:41 +0000 [thread overview] Message-ID: <bug-107954-4-7McTtXDX3a@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 #3 from joseph at codesourcery dot com <joseph at codesourcery dot com> --- Editorial review before the CD ballot slipped the schedule. Second-round editorial review after a huge number of changes in the editorial review slipped the schedule. Getting a final draft with all the changes into the CD ballot process slipped the schedule. The January meeting is two weeks later than originally planned because of the schedule delays. I just sent 206 comments on the CD to BSI for submission to ISO as the UK comments and if other NBs have similar numbers of comments, (a) it wouldn't surprise me if there's difficulty in getting through all of them in a single week's meeting (even if we find a way not to need to discuss all the editorial comments individually in the meeting) and (b) there could easily be further delays getting all the changes into the working draft and reviewed for being correctly applied. So despite the 56-day "ISO editing" period on the schedule before the DIS ballot (which may be meant to deal with all the editorial issues ISO comes up with at the last minute), it's entirely plausible there could be schedule slip for the DIS ballot - even supposing we don't need any extra ballot stages (CD2 or FDIS). So while it's possible that the new standard will be published in 2023 - or with a __STDC_VERSION__ value from 2023 even if published in 2024 - there is plenty of scope for the schedule to slip given the amount of work that still needs to be done on the draft.
next prev parent reply other threads:[~2022-12-07 0:41 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 [this message] 2023-08-10 23:07 ` romain.geissler at amadeus dot com 2023-08-11 15:48 ` joseph at codesourcery dot com 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-7McTtXDX3a@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: linkBe 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).