nightmorph 09/06/26 03:33:21 Modified: gcc-optimization.xml Log: update options and links to gcc 4.3
Revision Changes Path 1.15 xml/htdocs/doc/en/gcc-optimization.xml file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-optimization.xml?rev=1.15&view=markup plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-optimization.xml?rev=1.15&content-type=text/plain diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-optimization.xml?r1=1.14&r2=1.15 Index: gcc-optimization.xml =================================================================== RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-optimization.xml,v retrieving revision 1.14 retrieving revision 1.15 diff -u -r1.14 -r1.15 --- gcc-optimization.xml 22 Jul 2008 05:56:05 -0000 1.14 +++ gcc-optimization.xml 26 Jun 2009 03:33:21 -0000 1.15 @@ -1,6 +1,6 @@ <?xml version='1.0' encoding='UTF-8'?> <!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> -<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-optimization.xml,v 1.14 2008/07/22 05:56:05 nightmorph Exp $ --> +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-optimization.xml,v 1.15 2009/06/26 03:33:21 nightmorph Exp $ --> <guide link="/doc/en/gcc-optimization.xml"> <title>Compilation Optimization Guide</title> @@ -19,8 +19,8 @@ <!-- See http://creativecommons.org/licenses/by-sa/2.5 --> <license/> -<version>1.9</version> -<date>2008-07-21</date> +<version>1.10</version> +<date>2009-06-25</date> <chapter> <title>Introduction</title> @@ -39,7 +39,7 @@ They can be used to decrease the amount of debug messages for a program, increase error warning levels, and, of course, to optimize the code produced. The <uri -link="http://gcc.gnu.org/onlinedocs/gcc-4.1.2/gcc/Invoking-GCC.html#Invoking-GCC";>GNU +link="http://gcc.gnu.org/onlinedocs/gcc-4.3.3/gcc/Invoking-GCC.html#Invoking-GCC";>GNU gcc handbook</uri> maintains a complete list of available options and their purposes. </p> @@ -139,7 +139,7 @@ <note> Whenever you're not sure what a flag actually does, refer to the relevant chapter of the <uri -link="http://gcc.gnu.org/onlinedocs/gcc-4.1.2/gcc/Optimize-Options.html#Optimize-Options";>gcc +link="http://gcc.gnu.org/onlinedocs/gcc-4.3.3/gcc/Optimize-Options.html#Optimize-Options";>gcc manual</uri>. If you're still stumped, try Google, or check out the <c>gcc</c> <uri link="http://gcc.gnu.org/lists.html";>mailing lists</uri>. </note> @@ -224,7 +224,7 @@ x86/x86-64) . . . but with a different flag name. Again, <c>gcc</c>'s behavior and flag naming just isn't consistent across architectures, so be sure to check the <c>gcc</c> <uri -link="http://gcc.gnu.org/onlinedocs/gcc-4.1.2/gcc/Submodel-Options.html#Submodel-Options";>manual</uri> +link="http://gcc.gnu.org/onlinedocs/gcc-4.3.3/gcc/Submodel-Options.html#Submodel-Options";>manual</uri> to determine which one you should use for your system. </p> @@ -233,7 +233,7 @@ read chapter 5 of the appropriate <uri link="/doc/en/handbook/">Gentoo Installation Handbook</uri> for your arch. Also, read the <c>gcc</c> manual's list of <uri -link="http://gcc.gnu.org/onlinedocs/gcc-4.1.2/gcc/Submodel-Options.html#Submodel-Options";>architecture-specific +link="http://gcc.gnu.org/onlinedocs/gcc-4.3.3/gcc/Submodel-Options.html#Submodel-Options";>architecture-specific options</uri>, as well as more detailed explanations about the differences between <c>-march</c>, <c>-mcpu</c>, and <c>-mtune</c>. </note> @@ -259,7 +259,7 @@ <p> With the exception of <c>-O0</c>, the <c>-O</c> settings each activate several additional flags, so be sure to read the gcc manual's chapter on <uri -link="http://gcc.gnu.org/onlinedocs/gcc-4.1.2/gcc/Optimize-Options.html#Optimize-Options";>optimization +link="http://gcc.gnu.org/onlinedocs/gcc-4.3.3/gcc/Optimize-Options.html#Optimize-Options";>optimization options</uri> to learn which flags are activated at each <c>-O</c> level, as well as some explanations as to what they do. </p> @@ -404,7 +404,7 @@ <note> You should check the <uri -link="http://gcc.gnu.org/onlinedocs/gcc-4.1.2/gcc/i386-and-x86_002d64-Options.html#i386-and-x86_002d64-Options";>list</uri> +link="http://gcc.gnu.org/onlinedocs/gcc-4.3.3/gcc/i386-and-x86_002d64-Options.html#i386-and-x86_002d64-Options";>list</uri> of x86 and x86-64-specific flags to see which of these instruction sets are activated by the proper CPU type flag. If an instruction is listed, then you don't need to specify it; it will be turned on by using the proper <c>-march</c> @@ -425,7 +425,7 @@ No, you only <e>think</e> you do because someone has convinced you that more flags are better. Aggressive flags will only hurt your applications when used system-wide. Even the <c>gcc</c> <uri -link="http://gcc.gnu.org/onlinedocs/gcc-4.1.2/gcc/Optimize-Options.html#Optimize-Options";>manual</uri> +link="http://gcc.gnu.org/onlinedocs/gcc-4.3.3/gcc/Optimize-Options.html#Optimize-Options";>manual</uri> says that using <c>-funroll-loops</c> and <c>-funroll-all-loops</c> makes code larger and run more slowly. Yet for some reason, these two flags, along with <c>-ffast-math</c>, <c>-fforce-mem</c>, <c>-fforce-addr</c>, and similar flags, @@ -587,7 +587,7 @@ <ul> <li> - The <uri link="http://gcc.gnu.org/onlinedocs/gcc-4.1.2/gcc/";>GNU gcc + The <uri link="http://gcc.gnu.org/onlinedocs/gcc-4.3.3/gcc/";>GNU gcc manual</uri> </li> <li>
