| Message ID | 20201126095843.16031-1-mhillen@linux.ibm.com |
|---|---|
| State | New |
| Headers | show |
| Series | gcc-11/changes: Document new configure flag --enable-s390-excess-float-precision | expand |
On 11/26/20 2:58 AM, Marius Hillenbrand via Gcc-patches wrote: > Hi, > > To document the new behavior around FLT_EVAL_METHOD and configure flag > --enable-s390-excess-float-precision on s390, I propose this update to the > Release Notes. Please commit to git-wwwdocs if you agree. > > Checked against the w3c validator. > > Thanks, > Marius > --- > htdocs/gcc-11/changes.html | 15 ++++++++++++++- > 1 file changed, 14 insertions(+), 1 deletion(-) Thanks. Pushed to the trunk. jeff
On Thu, 26 Nov 2020, Marius Hillenbrand via Gcc-patches wrote: > To document the new behavior around FLT_EVAL_METHOD and configure flag > --enable-s390-excess-float-precision on s390, I propose this update to > the Release Notes. Please commit to git-wwwdocs if you agree. Thank you, Marius, and thank you Jeff for committing this. I applied the follow up below since when refering to the project, as opposed to just the C compiler, we use GCC (as opposed to gcc). Gerald 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>
diff --git a/htdocs/gcc-11/changes.html b/htdocs/gcc-11/changes.html index 46a6a372..20f29677 100644 --- a/htdocs/gcc-11/changes.html +++ b/htdocs/gcc-11/changes.html @@ -340,7 +340,20 @@ a work-in-progress.</p> <!-- <h3 id="powerpc">PowerPC / PowerPC64 / RS6000</h3> --> -<!-- <h3 id="s390">S/390, System z, IBM z Systems</h3> --> +<h3 id="s390">S/390, System z, IBM Z Systems</h3> +<ul> + <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 + 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. + </li> +</ul> <!-- <h3 id="riscv">RISC-V</h3> -->