I pushed a minor update to the existing entry for s390-specific
--enable-s390-excess-float-precision after validating.
Marius
--->8--------->8---------->8--------->8-------
Reflect the changes in commit 33f925094d02 ("IBM Z: Detect libc's
float_t behavior on cross compiles").
---
htdocs/gcc-11/changes.html | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/htdocs/gcc-11/changes.html b/htdocs/gcc-11/changes.html
index 08a4c93a..13a35e09 100644
--- a/htdocs/gcc-11/changes.html
+++ b/htdocs/gcc-11/changes.html
@@ -466,9 +466,9 @@ a work-in-progress.</p>
maintain previous behavior and evaluate float expressions in double
precision, which aligns with the definition of <code>float_t</code> as
<code>double</code>. With the flag disabled, GCC will always evaluate
- float expressions in single precision. In native builds, GCC will by
- default match the definition of <code>float_t</code> in the installed
- glibc.
+ float expressions in single precision. In native builds and cross
compiles
+ that have target libc headers, GCC will by default match the definition
of
+ <code>float_t</code> in the installed glibc.
</li>
</ul>
--
2.26.2
