On Wed, 6 Apr 2022, Xi Ruoyao via Gcc-patches wrote:
> Document ABI changes in r12-7961, 7962, and 8023. Ok for wwwdocs?
Thank you!
Note <a name=...> is deprecated, and we generally use id= attributes.
I made this change, and also expanded the anchor from just "ABI" which
is very generic to more specific text.
Pushed on top of the original changes.
Gerald
diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
index 60ed4b32..d645b15f 100644
--- a/htdocs/gcc-12/changes.html
+++ b/htdocs/gcc-12/changes.html
@@ -709,8 +709,8 @@ function Multiply (S1, S2 : Sign) return Sign is
<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
+ <li>The <a id="mips_zero_width_fields">ABI passing arguments
+ containing zero-width fields</a> (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
@@ -718,8 +718,8 @@ function Multiply (S1, S2 : Sign) return Sign is
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
+ <li>The <a id="mips_cxx17_empty_bases">ABI returning values
+ containing C++17 empty bases</a> 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
