public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Joseph Myers <jsm28@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. caa5dc6995aac2c7dc1a139e1a021927faaf73eb Date: Fri, 25 Mar 2022 23:12:41 +0000 (GMT) [thread overview] Message-ID: <20220325231241.0EE543858D37@sourceware.org> (raw) This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "gcc-wwwdocs". The branch, master has been updated via caa5dc6995aac2c7dc1a139e1a021927faaf73eb (commit) from e870a90578545e04dea26cd9d9aa32dff2212834 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit caa5dc6995aac2c7dc1a139e1a021927faaf73eb Author: Joseph Myers <joseph@codesourcery.com> Date: Fri Mar 25 23:12:16 2022 +0000 Add release notes for new C2X features in GCC 12 diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html index 9cff81b9..689feeba 100644 --- a/htdocs/gcc-12/changes.html +++ b/htdocs/gcc-12/changes.html @@ -193,6 +193,27 @@ a work-in-progress.</p> </li> </ul> +<h3 id="c">C</h3> +<ul> + <li>Some new features from the upcoming C2X revision of the ISO C + standard are supported with <code>-std=c2x</code> + and <code>-std=gnu2x</code>. Some of these features are also + supported as extensions when compiling for older language versions. + In addition to the features listed, some features previously + supported as extensions and now added to the C standard are enabled + by default in C2X mode and not diagnosed with <code>-std=c2x + -Wpedantic</code>. + <ul> + <li>Digit separators (as in C++) are supported for C2X.</li> + <li>The <code>#elifdef</code> and <code>#elifndef</code> + preprocessing directives are now supported.</li> + <li>The <code>printf</code> and <code>scanf</code> format checking + with <code>-Wformat</code> now supports the <code>%b</code> format + specified by C2X for binary integers, and the <code>%B</code> + format recommended by C2X for <code>printf</code>. + </ul></li> +</ul> + <h3 id="cxx">C++</h3> <ul> <li>Several C++23 features have been implemented: ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-12/changes.html | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2022-03-25 23:12 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220325231241.0EE543858D37@sourceware.org \ --to=jsm28@sourceware.org \ --cc=gcc-cvs-wwwdocs@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).