public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Gerald Pfeifer <gerald@pfeifer.com>,
	"Joseph S. Myers" <joseph@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org
Subject: [wwwdocs] Mention the GNU C enum changes in gcc-13/changes.html
Date: Fri, 24 Mar 2023 12:37:39 +0100	[thread overview]
Message-ID: <ZB2LgwL5rK/JI+KH@tucnak> (raw)

Hi!

The following patch attempts to document the PR36113 changes to the
GNU C extension support of enumerators which don't fit into int.

Ok for wwwdocs?

Shall we mention it in porting_to.html as well?
The only known affected package is (was?) the Linux kernel.

diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html
index f8e9560c..d2035435 100644
--- a/htdocs/gcc-13/changes.html
+++ b/htdocs/gcc-13/changes.html
@@ -59,6 +59,22 @@ a work-in-progress.</p>
       <a href="https://gcc.gnu.org/onlinedocs/gcc-12.2.0/gcc/ARM-iWMMXt-Built-in-Functions.html">
       iWMMXt built-in functions</a>.
     </li>
+    <li>The behavior of the GNU C extension support of enumerators which
+      don't fit into <code>int</code> has been changed to match the C2X
+      behavior.  Previously, in enumerations where at least one enumerator
+      didn't fit into <code>int</code>, only those enumerators that didn't
+      fit into <code>int</code> had the <code>enum</code> type and others
+      had <code>int</code> type and while the <code>enum</code> is being
+      defined enumerators that didn't fit into <code>int</code> had some
+      unspecified type with the sign and precision of its value.
+      In GCC13, in such enumerations all enumerators have the
+      <code>enum</code> type and while the <code>enum</code> is being
+      defined enumerators that didn't fit into <code>int</code> have
+      type of their value.  If all enumerators fit into <code>int</code>
+      type, as before all enumerators have <code>int</code> type, both
+      while the <code>enum</code> is being defined and after it is defined.
+      See <a href="https://gcc.gnu.org/PR36113">PR36113</a> for details.
+    </li>
 </ul>
 
 

	Jakub


             reply	other threads:[~2023-03-24 12:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-24 11:37 Jakub Jelinek [this message]
2023-03-30 23:07 ` Gerald Pfeifer

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=ZB2LgwL5rK/JI+KH@tucnak \
    --to=jakub@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gerald@pfeifer.com \
    --cc=joseph@codesourcery.com \
    /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).