Update according to the amendment made for GCC 4.0.0 with commit
b11a9d5f3f90 back in 2004:
(mips_arg_info): Don't allow fpr_p to affect the register or
stack alignment. Remove o64 silliness.
Retain the description of the former semantics for reference.
---
htdocs/projects/mipso64-abi.html | 13 ++++++++-----
1 file changed, 8 insertions(+), 5 deletions(-)
diff --git a/htdocs/projects/mipso64-abi.html b/htdocs/projects/mipso64-abi.html
index 6cd60c22..8a2a6618 100644
--- a/htdocs/projects/mipso64-abi.html
+++ b/htdocs/projects/mipso64-abi.html
@@ -39,11 +39,14 @@ packed towards the upper-address side.
<h2>Floating-Point Arguments</h2>
-If the first and second arguments floating-point arguments to a
-function are 32-bit values, they are passed in <code>$f12</code> and
-<code>$f14</code>. If the first is a 32-bit value and the second is a
-64-bit value, they are passed in <code>$f12</code> and
-<code>$f13</code>. If they are both 64-bit values, they are passed in
+As from GCC 4.0.0 the first and second floating-point arguments to a
+function are passed in <code>$f12</code> and <code>$f14</code>.
+
+Previously if the first and second floating-point arguments to a
+function were 32-bit values, they were passed in <code>$f12</code> and
+<code>$f14</code>. If the first was a 32-bit value and the second was a
+64-bit value, they were passed in <code>$f12</code> and
+<code>$f13</code>. If they were both 64-bit values, they were passed in
<code>$f12</code> and <code>$f13</code>.
<h2>ELF Header</h2>
--
2.20.1
