From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id DD399384C93B; Wed, 7 Dec 2022 00:41:43 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org DD399384C93B DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1670373703; bh=eNdTLf2xs9rvqwaI7h2IfHnbblZfj90mn4h3aZMmwxM=; h=From:To:Subject:Date:In-Reply-To:References:From; b=biHq2ol3deskcWVTOTC+MYX0I5Cg4Vptq45fwblSMBSlTkgZEHi6kd61gsefBEAsi fW3Z8/izpfCwEKR7YuxV/6yCRKDWmIhKDv8w6Ye6LWP/QCgekjlCuQq6h2+3ePZqIX PE/alG4cFEhc5OkhZIYbF1APHOuSMif0iKnx9uEY= From: "joseph at codesourcery dot com" 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c X-Bugzilla-Version: 13.0 X-Bugzilla-Keywords: diagnostic, documentation, internal-improvement X-Bugzilla-Severity: normal X-Bugzilla-Who: joseph at codesourcery dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D107954 --- Comment #3 from joseph at codesourcery dot com --- Editorial review before the CD ballot slipped the schedule. Second-round=20 editorial review after a huge number of changes in the editorial review=20 slipped the schedule. Getting a final draft with all the changes into the= =20 CD ballot process slipped the schedule. The January meeting is two weeks=20 later than originally planned because of the schedule delays. I just sent= =20 206 comments on the CD to BSI for submission to ISO as the UK comments and= =20 if other NBs have similar numbers of comments, (a) it wouldn't surprise me= =20 if there's difficulty in getting through all of them in a single week's=20 meeting (even if we find a way not to need to discuss all the editorial=20 comments individually in the meeting) and (b) there could easily be=20 further delays getting all the changes into the working draft and reviewed= =20 for being correctly applied. So despite the 56-day "ISO editing" period=20 on the schedule before the DIS ballot (which may be meant to deal with all= =20 the editorial issues ISO comes up with at the last minute), it's entirely=20 plausible there could be schedule slip for the DIS ballot - even supposing= =20 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 -=20 or with a __STDC_VERSION__ value from 2023 even if published in 2024 -=20 there is plenty of scope for the schedule to slip given the amount of work= =20 that still needs to be done on the draft.=