public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Xi Ruoyao <xry111@mengyan1223.wang>
To: gcc-patches@gcc.gnu.org
Cc: Richard Sandiford <richard.sandiford@arm.com>,
	Jakub Jelinek <jakub@gcc.gnu.org>,
	YunQiang Su <yunqiang.su@cipunited.com>
Subject: [wwwdocs PATCH v2] document zero-width field ABI changes on MIPS
Date: Wed, 06 Apr 2022 23:26:54 +0800	[thread overview]
Message-ID: <6144a58c030ee034e7f4d9cf481045c7b7c07af2.camel@mengyan1223.wang> (raw)
In-Reply-To: <bf6b80e390235055af767a380a75138883b39bb8.camel@mengyan1223.wang>

Document ABI changes in r12-7961, 7962, and 8023.  Ok for wwwdocs?

---
 htdocs/gcc-12/changes.html | 25 ++++++++++++++++++++++++-
 1 file changed, 24 insertions(+), 1 deletion(-)

diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
index 4f2ee77f..c924bca3 100644
--- a/htdocs/gcc-12/changes.html
+++ b/htdocs/gcc-12/changes.html
@@ -50,6 +50,10 @@ a work-in-progress.</p>
     (so there is a C++ ABI incompatibility, GCC 4.4 and earlier compatible
     with GCC 12 or later, incompatible with GCC 4.5 through GCC 11).
     RISC-V has changed the handling of these already starting with GCC 10.
+    As the ABI requires, MIPS takes them into account handling function
+    return values so there is a C++ ABI incompatibility with GCC 4.5
+    through 11.  For function arguments on MIPS, refer to
+    <a href="#mips_zero_width_fields">the MIPS specific entry</a>.
     GCC 12 on the above targets will report such incompatibilities as
     warnings or other diagnostics unless <code>-Wno-psabi</code> is used.
   </li>
@@ -549,7 +553,26 @@ a work-in-progress.</p>
   </li>
 </ul>
 
-<!-- <h3 id="mips">MIPS</h3> -->
+<h3 id="mips">MIPS</h3>
+<ul>
+  <li>The <a name="mips_zero_width_fields">ABI</a> passing arguments
+      containing zero-width fields (for example, C/C++ zero-width
+      bit-fields, GNU C/C++ zero-length arrays, and GNU C empty structs)
+      has changed.  Now a zero-width field will not prevent an aligned
+      64-bit floating-point field next to it from being passed through
+      FPR.  This is compatible with LLVM, but incompatible with previous
+      GCC releases. GCC 12 on MIPS will report such incompatibilities as
+      an inform unless <code>-Wno-psabi</code> is used.
+  </li>
+  <li>The <a name="mips_cxx17_empty_bases">ABI</a> returning values
+      containing C++17 empty bases has changed.  Now an empty base will
+      not prevent an aggregate containing only one or two floating-point
+      fields from being returned through FPR.  This is compatible with
+      GCC 6 and earlier, but incompatible with GCC 7 through 11. GCC 12 on
+      MIPS will report such incompatibilities as an inform unless
+      <code>-Wno-psabi</code> is used.
+  </li>
+</ul>
 
 <!-- <h3 id="mep">MeP</h3> -->
 
-- 
2.35.1



  reply	other threads:[~2022-04-06 15:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-01 16:32 [wwwdocs PATCH] " Xi Ruoyao
2022-04-06 15:26 ` Xi Ruoyao [this message]
2022-04-28 17:28   ` [PING wwwdocs PATCH v2] " Xi Ruoyao
2022-04-29  6:51     ` Richard Biener
2022-05-12  7:00   ` [wwwdocs " 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=6144a58c030ee034e7f4d9cf481045c7b7c07af2.camel@mengyan1223.wang \
    --to=xry111@mengyan1223.wang \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@gcc.gnu.org \
    --cc=richard.sandiford@arm.com \
    --cc=yunqiang.su@cipunited.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).