public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
* [committed][gcc-wwwdocs] Add blurb about bitfield signedness on mcore
@ 2023-12-20  4:29 Jeff Law
  2024-02-07 21:23 ` Gerald Pfeifer
  0 siblings, 1 reply; 3+ messages in thread
From: Jeff Law @ 2023-12-20  4:29 UTC (permalink / raw)
  To: gcc-patches

[-- 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> -->

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [committed][gcc-wwwdocs] Add blurb about bitfield signedness on mcore
  2023-12-20  4:29 [committed][gcc-wwwdocs] Add blurb about bitfield signedness on mcore Jeff Law
@ 2024-02-07 21:23 ` Gerald Pfeifer
  2024-02-08  0:47   ` Jeff Law
  0 siblings, 1 reply; 3+ messages in thread
From: Gerald Pfeifer @ 2024-02-07 21:23 UTC (permalink / raw)
  To: Jeff Law; +Cc: gcc-patches

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>
 

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [committed][gcc-wwwdocs] Add blurb about bitfield signedness on mcore
  2024-02-07 21:23 ` Gerald Pfeifer
@ 2024-02-08  0:47   ` Jeff Law
  0 siblings, 0 replies; 3+ messages in thread
From: Jeff Law @ 2024-02-08  0:47 UTC (permalink / raw)
  To: Gerald Pfeifer; +Cc: gcc-patches



On 2/7/24 14:23, Gerald Pfeifer wrote:
> 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?
Yes, of course.

Thanks.
jeff

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2024-02-08  0:47 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-12-20  4:29 [committed][gcc-wwwdocs] Add blurb about bitfield signedness on mcore Jeff Law
2024-02-07 21:23 ` Gerald Pfeifer
2024-02-08  0:47   ` Jeff Law

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).