| Message ID | alpine.LSU.2.20.1504122347300.9357@tuna.site |
|---|---|
| State | New |
| Headers | show |
No feedback, so I now went ahead and applied this. Tobias, if you have any suggestions, please advise. Gerald On Sun, 12 Apr 2015, Gerald Pfeifer wrote: > [ Tobias, your burnus@net-b.de account just bounced with "mailbox full"! ] > > On Tue, 18 Feb 2014, Tobias Burnus wrote: >> is the wording okay - and/or do you have further suggestions? > > Here are some suggestions on top of the existing text. > > Remove a comma and break a long sentence in the SIMD section. > Use "least significant" instead of "last significant" when > refering to rounding and simplify a sentence in the Fortran > section. > > I have not committed this yet since the sentence on rounding > really feels rather weird. Should there be something like > "whereas compatible would round..." (as opposed to "rounds")? > > Gerald > > Index: changes.html > =================================================================== > RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.9/changes.html,v > retrieving revision 1.85 > diff -u -r1.85 changes.html > --- changes.html 8 Apr 2015 10:33:06 -0000 1.85 > +++ changes.html 12 Apr 2015 21:47:26 -0000 > @@ -127,11 +127,11 @@ > >OpenMP specification</a> is now supported in the C and C++ compilers > and starting with the 4.9.1 release also in the Fortran compiler. > The new <code>-fopenmp-simd</code> option can be used to enable OpenMP's > - SIMD directives, while ignoring other OpenMP directives. The new <a > + SIMD directives while ignoring other OpenMP directives. The new <a > href="https://gcc.gnu.org/onlinedocs/gcc-4.9.2/gcc/Optimize-Options.html#index-fsimd-cost-model-908" > ><code>-fsimd-cost-model=</code></a> option permits to tune the > vectorization cost model for loops annotated with OpenMP and Cilk > - Plus <code>simd</code> directives; <code>-Wopenmp-simd</code> warns when > + Plus <code>simd</code> directives. <code>-Wopenmp-simd</code> warns when > the current cost model overrides simd directives set by the user.</li> > <li>The <code>-Wdate-time</code> option has been added for the C, C++ and > Fortran compilers, which warns when the <code>__DATE__</code>, > @@ -459,9 +459,9 @@ > <code>strtod</code> honours the rounding mode. (For output, rounding is > supported since GCC 4.5.) Note that for input, the > <code>compatible</code> rounding mode is handled as <code>nearest</code> > - (i.e., for a tie, rounding to an even last significant > - [cf. IEC 60559:1989] – while <code>compatible</code> rounds away > - from zero for a tie).</li> > + (i.e., rounding to an even least significant [cf. IEC 60559:1989] > + for a tie, while <code>compatible</code> rounds away from zero in > + that case).</li> > </ul></li> > </ul>
Index: changes.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.9/changes.html,v retrieving revision 1.85 diff -u -r1.85 changes.html --- changes.html 8 Apr 2015 10:33:06 -0000 1.85 +++ changes.html 12 Apr 2015 21:47:26 -0000 @@ -127,11 +127,11 @@ >OpenMP specification</a> is now supported in the C and C++ compilers and starting with the 4.9.1 release also in the Fortran compiler. The new <code>-fopenmp-simd</code> option can be used to enable OpenMP's - SIMD directives, while ignoring other OpenMP directives. The new <a + SIMD directives while ignoring other OpenMP directives. The new <a href="https://gcc.gnu.org/onlinedocs/gcc-4.9.2/gcc/Optimize-Options.html#index-fsimd-cost-model-908" ><code>-fsimd-cost-model=</code></a> option permits to tune the vectorization cost model for loops annotated with OpenMP and Cilk - Plus <code>simd</code> directives; <code>-Wopenmp-simd</code> warns when + Plus <code>simd</code> directives. <code>-Wopenmp-simd</code> warns when the current cost model overrides simd directives set by the user.</li> <li>The <code>-Wdate-time</code> option has been added for the C, C++ and Fortran compilers, which warns when the <code>__DATE__</code>, @@ -459,9 +459,9 @@ <code>strtod</code> honours the rounding mode. (For output, rounding is supported since GCC 4.5.) Note that for input, the <code>compatible</code> rounding mode is handled as <code>nearest</code> - (i.e., for a tie, rounding to an even last significant - [cf. IEC 60559:1989] – while <code>compatible</code> rounds away - from zero for a tie).</li> + (i.e., rounding to an even least significant [cf. IEC 60559:1989] + for a tie, while <code>compatible</code> rounds away from zero in + that case).</li> </ul></li> </ul>
[ Tobias, your burnus@net-b.de account just bounced with "mailbox full"! ] On Tue, 18 Feb 2014, Tobias Burnus wrote: > is the wording okay - and/or do you have further suggestions? Here are some suggestions on top of the existing text. Remove a comma and break a long sentence in the SIMD section. Use "least significant" instead of "last significant" when refering to rounding and simplify a sentence in the Fortran section. I have not committed this yet since the sentence on rounding really feels rather weird. Should there be something like "whereas compatible would round..." (as opposed to "rounds")? Gerald