This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: PATCH: Mention x86 configure changes for gcc 4.5.0
On Sun, Apr 4, 2010 at 07:01, Gerald Pfeifer <gerald@pfeifer.com> wrote:
> Actually, if you could use "command-line option" or "option" instead
> of "flag", that would be preferrable.
>
I replaced all the uses of "flag" with "option" in that file.
Ok to commit?
Thanks,
Sebastian
*** changes.html 31 Mar 2010 16:09:46 -0500 1.78
--- changes.html 04 Apr 2010 10:21:30 -0500
***************
*** 66,72 ****
run significantly slower when compiled with GCC 4.5 in strict C99
conformance mode than they did with earlier GCC versions. This is due
to stricter standard conformance of the compiler and can be avoided by
! using the flag <code>-fexcess-precision=fast</code>; also see
<a href="#x86">below</a>.</li>
</ul>
--- 66,72 ----
run significantly slower when compiled with GCC 4.5 in strict C99
conformance mode than they did with earlier GCC versions. This is due
to stricter standard conformance of the compiler and can be avoided by
! using the option <code>-fexcess-precision=fast</code>; also see
<a href="#x86">below</a>.</li>
</ul>
***************
*** 114,120 ****
<li>A new link-time optimizer has been added (<code><a
href="http://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html#index-flto-795";
>-flto</a></code>).
! When this flag is used, GCC generates a bytecode representation of
each input file and writes it to special ELF sections in each
object file. When the object files are linked together, all the
function bodies are read from these ELF sections and instantiated
--- 114,120 ----
<li>A new link-time optimizer has been added (<code><a
href="http://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html#index-flto-795";
>-flto</a></code>).
! When this option is used, GCC generates a bytecode representation of
each input file and writes it to special ELF sections in each
object file. When the object files are linked together, all the
function bodies are read from these ELF sections and instantiated
***************
*** 268,274 ****
<li>Access control is now applied to <code>typedef</code> names used in
a template, which may cause G++ to reject some ill-formed code that was
accepted by earlier releases. The <code>-fno-access-control</code>
! flag can be used as a temporary workaround until the code is
corrected.</li>
<li>Compilation time for code that uses templates should now scale
--- 268,274 ----
<li>Access control is now applied to <code>typedef</code> names used in
a template, which may cause G++ to reject some ill-formed code that was
accepted by earlier releases. The <code>-fno-access-control</code>
! option can be used as a temporary workaround until the code is
corrected.</li>
<li>Compilation time for code that uses templates should now scale
***************
*** 414,429 ****
instead of adding the padding before a variable it is now added
afterwards, which increases the compatibility with other vendors
and helps to obtain the correct output in some cases. Cf. also the
! <code>-falign-commons</code> flag (<a href="../gcc-4.4/changes.html">added
in 4.4</a>).</li>
! <li>The <code>-finit-real=</code> flag now also supports the value
<code>snan</code> for signalling not-a-number; to be effective,
one additionally needs to enable trapping (e.g. via
<code>-ffpe-trap=</code>). Note: Compile-time optimizations can
turn a signalling NaN into a quiet one.</li>
! <li>The new flag <code>-fcheck=</code> has been added with the
options <code>bounds</code>, <code>array-temps</code>,
<code>do</code>, <code>pointer</code>, and <code>recursive</code>. The
<code>bounds</code> and <code>array-temps</code> options are
--- 414,429 ----
instead of adding the padding before a variable it is now added
afterwards, which increases the compatibility with other vendors
and helps to obtain the correct output in some cases. Cf. also the
! <code>-falign-commons</code> option (<a
href="../gcc-4.4/changes.html">added
in 4.4</a>).</li>
! <li>The <code>-finit-real=</code> option now also supports the value
<code>snan</code> for signalling not-a-number; to be effective,
one additionally needs to enable trapping (e.g. via
<code>-ffpe-trap=</code>). Note: Compile-time optimizations can
turn a signalling NaN into a quiet one.</li>
! <li>The new option <code>-fcheck=</code> has been added with the
options <code>bounds</code>, <code>array-temps</code>,
<code>do</code>, <code>pointer</code>, and <code>recursive</code>. The
<code>bounds</code> and <code>array-temps</code> options are
***************
*** 441,447 ****
about invalid string lengths of character dummy arguments. Additionally,
more compile-time checks have been added.</li>
! <li>The new flag <a
href="http://gcc.gnu.org/onlinedocs/gfortran/Code-Gen-Options.html";
><code>-fno-protect-parens</code></a> has been added; if set, the
compiler may reorder REAL and COMPLEX expressions without regard
--- 441,447 ----
about invalid string lengths of character dummy arguments. Additionally,
more compile-time checks have been added.</li>
! <li>The new option <a
href="http://gcc.gnu.org/onlinedocs/gfortran/Code-Gen-Options.html";
><code>-fno-protect-parens</code></a> has been added; if set, the
compiler may reorder REAL and COMPLEX expressions without regard
***************
*** 463,469 ****
<li>Array assignments and <code>WHERE</code> are now run in parallel when
OpenMP's <code>WORKSHARE</code> is used.</li>
! <li>The experimental flag <code>-fwhole-file</code> was added. The flag
allows whole-file checking of procedure arguments and allows for better
optimizations. It can also be used with <code>-fwhole-program</code>,
which is now also supported in gfortran.</li>
--- 463,469 ----
<li>Array assignments and <code>WHERE</code> are now run in parallel when
OpenMP's <code>WORKSHARE</code> is used.</li>
! <li>The experimental option <code>-fwhole-file</code> was added.
The option
allows whole-file checking of procedure arguments and allows for better
optimizations. It can also be used with <code>-fwhole-program</code>,
which is now also supported in gfortran.</li>
***************
*** 601,611 ****
<li>Support for the XOP, FMA4, and LWP instruction sets for the AMD
Orochi processors are now available with
the <code>-mxop</code>, <code>-mfma4</code>,
! and <code>-mlwp</code> flags.</li>
! <li> The <code>-mabm</code> flag enables GCC to use
the <code>popcnt</code> and <code>lzcnt</code> instructions on AMD
processors.</li>
! <li> The <code>-mpopcnt</code> flag enables GCC to use
the <code>popcnt</code> instructions on both AMD and Intel
processors.</li>
</ul>
--- 601,611 ----
<li>Support for the XOP, FMA4, and LWP instruction sets for the AMD
Orochi processors are now available with
the <code>-mxop</code>, <code>-mfma4</code>,
! and <code>-mlwp</code> options.</li>
! <li> The <code>-mabm</code> option enables GCC to use
the <code>popcnt</code> and <code>lzcnt</code> instructions on AMD
processors.</li>
! <li> The <code>-mpopcnt</code> option enables GCC to use
the <code>popcnt</code> instructions on both AMD and Intel
processors.</li>
</ul>