public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@pfeifer.com>
To: Jeff Law <jeffreyalaw@gmail.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [committed][gcc-wwwdocs] Add blurb about bitfield signedness on mcore
Date: Wed, 7 Feb 2024 22:23:13 +0100 (CET)	[thread overview]
Message-ID: <b8a7a6a2-06ee-6b7d-dad7-5c7b9a536980@pfeifer.com> (raw)
In-Reply-To: <4f228ab7-cc8f-4ca7-b32c-58e530771796@gmail.com>

On Tue, 19 Dec 2023, Jeff Law wrote:
> Pushed to the trunk.

Is this minor follow-up okay, adding a full stop and shortening a bit?

Gerald

diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
index 6d917535..dbc77493 100644
--- a/htdocs/gcc-14/changes.html
+++ b/htdocs/gcc-14/changes.html
@@ -504,7 +504,7 @@ a work-in-progress.</p>
 <!-- <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>
+    to be unsigned, use <code>-funsigned-bitfields</code>.
   </li>
 </ul>
 

  reply	other threads:[~2024-02-07 21:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-20  4:29 Jeff Law
2024-02-07 21:23 ` Gerald Pfeifer [this message]
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=b8a7a6a2-06ee-6b7d-dad7-5c7b9a536980@pfeifer.com \
    --to=gerald@pfeifer.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jeffreyalaw@gmail.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).