From: Joseph Myers <josmyers@redhat.com>
To: gcc-patches@gcc.gnu.org
Subject: [committed] wwwdocs: gcc-14: Add release notes for C23 features
Date: Thu, 4 Apr 2024 17:05:46 +0000 (UTC) [thread overview]
Message-ID: <dc5f36f3-abee-984d-7bcc-2cb35fc88de8@redhat.com> (raw)
Add release notes for C23 features added in GCC 14. This doesn't
cover any non-C23 new C features; any such features should also have
release notes added.
diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
index 934cd1ad..045893cf 100644
--- a/htdocs/gcc-14/changes.html
+++ b/htdocs/gcc-14/changes.html
@@ -206,6 +206,31 @@ a work-in-progress.</p>
<!-- <h3 id="c-family">C family</h3> -->
+<h3 id="c">C</h3>
+
+<ul>
+ <li>Some more C23 features have been implemented:
+ <ul>
+ <li>Bit-precise integer types (<code>_BitInt (<i>N</i>)</code>
+ and <code>unsigned _BitInt (<i>N</i>)</code>): integer types with
+ a specified number of bits. These are only supported on
+ IA-32/x86-64 at present.</li>
+ <li>Structure, union and enumeration types may be defined more
+ than once in the same scope with the same contents and the same
+ tag; if such types are defined with the same contents and the
+ same tag in different scopes, the types are compatible.</li>
+ <li>The <code><stdckdint.h></code> header for checked
+ integer arithmetic.</li>
+ </ul>
+ </li>
+ <li>In addition to those C23 features, there are new command-line
+ options <code>-std=c23</code>, <code>-std=gnu23</code>
+ and <code>-Wc11-c23-compat</code>. These are equivalent to the
+ previous options <code>-std=c2x</code>, <code>-std=gnu2x</code>
+ and <code>-Wc11-c2x-compat</code>, which are deprecated but remain
+ supported.</li>
+</ul>
+
<h3 id="cxx">C++</h3>
<ul>
--
Joseph S. Myers
josmyers@redhat.com
reply other threads:[~2024-04-04 17:06 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=dc5f36f3-abee-984d-7bcc-2cb35fc88de8@redhat.com \
--to=josmyers@redhat.com \
--cc=gcc-patches@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).