This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "gcc-wwwdocs". The branch, master has been updated via aaf1c5103a16fba11e8c89766931be50df8a1ec9 (commit) from 86036cc93a01f7412165c486fc573acfcef50d7c (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit aaf1c5103a16fba11e8c89766931be50df8a1ec9 Author: Gerald Pfeifer <gerald@pfeifer.com> Date: Tue Dec 1 23:03:04 2020 +0100 Refer to our project as GCC diff --git a/htdocs/gcc-11/changes.html b/htdocs/gcc-11/changes.html index cd6e28c1..ed289744 100644 --- a/htdocs/gcc-11/changes.html +++ b/htdocs/gcc-11/changes.html @@ -345,11 +345,11 @@ a work-in-progress.</p> <li>The behavior when compiling with <code>-fexcess-precision=standard</code> (e.g., implied by <code>-std=c99</code>) on s390(x) targets can now be controlled at configure time with the flag - <code>--enable-s390-excess-float-precision</code>. When enabled, gcc will + <code>--enable-s390-excess-float-precision</code>. When enabled, GCC will 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 + <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. </li> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-11/changes.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) hooks/post-receive -- gcc-wwwdocs