From: Jeff Law <jeffreyalaw@gmail.com>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: [committed][gcc-wwwdocs] Add blurb about bitfield signedness on mcore
Date: Tue, 19 Dec 2023 21:29:12 -0700 [thread overview]
Message-ID: <4f228ab7-cc8f-4ca7-b32c-58e530771796@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 27 bytes --]
Pushed to the trunk.
jeff
[-- Attachment #2: P --]
[-- Type: text/plain, Size: 687 bytes --]
commit e56dc0003729ea6f7d26594dae34d218543edb49
Author: Jeff Law <jlaw@ventanamicro.com>
Date: Tue Dec 19 21:28:03 2023 -0700
Document that bitfields are signed on mcore now.
diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
index eb14e09d..11c7ca7e 100644
--- a/htdocs/gcc-14/changes.html
+++ b/htdocs/gcc-14/changes.html
@@ -341,6 +341,13 @@ a work-in-progress.</p>
</li>
</ul>
+<!-- <h3 id="mcore">MCore</h3> -->
+<ul>
+ <li>Bitfields are now signed by default per GCC policy. If you need bitfields
+ to be unsigned, then use <code>-funsigned-bitfields</code>
+ </li>
+</ul>
+
<!-- <h3 id="mips">MIPS</h3> -->
<!-- <h3 id="mep">MeP</h3> -->
next reply other threads:[~2023-12-20 4:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-20 4:29 Jeff Law [this message]
2024-02-07 21:23 ` Gerald Pfeifer
2024-02-08 0:47 ` Jeff Law
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=4f228ab7-cc8f-4ca7-b32c-58e530771796@gmail.com \
--to=jeffreyalaw@gmail.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).