public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Jeff Law <law@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. e56dc0003729ea6f7d26594dae34d218543edb49
Date: Wed, 20 Dec 2023 04:29:03 +0000 (GMT)	[thread overview]
Message-ID: <20231220042903.A08063857BA2@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  e56dc0003729ea6f7d26594dae34d218543edb49 (commit)
      from  b510ddfa655ce489ac7e02da5c8d76b712be9b51 (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 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> -->

-----------------------------------------------------------------------

Summary of changes:
 htdocs/gcc-14/changes.html | 7 +++++++
 1 file changed, 7 insertions(+)


hooks/post-receive
-- 
gcc-wwwdocs

                 reply	other threads:[~2023-12-20  4:29 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=20231220042903.A08063857BA2@sourceware.org \
    --to=law@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: 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).