nightmorph 10/07/27 00:24:29 Modified: gcc-optimization.xml Log: Update gcc docs, fix some basic GuideXML
Revision Changes Path 1.18 xml/htdocs/doc/en/gcc-optimization.xml file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/gcc-optimization.xml?rev=1.18&view=markup plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/gcc-optimization.xml?rev=1.18&content-type=text/plain diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/gcc-optimization.xml?r1=1.17&r2=1.18 Index: gcc-optimization.xml =================================================================== RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-optimization.xml,v retrieving revision 1.17 retrieving revision 1.18 diff -u -r1.17 -r1.18 --- gcc-optimization.xml 19 Oct 2009 16:16:36 -0000 1.17 +++ gcc-optimization.xml 27 Jul 2010 00:24:29 -0000 1.18 @@ -1,12 +1,12 @@ <?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.17 2009/10/19 16:16:36 neysx Exp $ --> +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-optimization.xml,v 1.18 2010/07/27 00:24:29 nightmorph Exp $ --> -<guide link="/doc/en/gcc-optimization.xml"> +<guide> <title>Compilation Optimization Guide</title> <author title="Author"> - <mail link="nightmo...@gentoo.org">Joshua Saddler</mail> + <mail link="nightmorph"/> </author> <abstract> @@ -19,8 +19,8 @@ <!-- See http://creativecommons.org/licenses/by-sa/2.5 --> <license/> -<version>1.12</version> -<date>2009-10-19</date> +<version>2</version> +<date>2010-07-26</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.3.3/gcc/Invoking-GCC.html#Invoking-GCC">GNU +link="http://gcc.gnu.org/onlinedocs/gcc-4.4.4/gcc/Invoking-GCC.html#Invoking-GCC">GNU gcc handbook</uri> maintains a complete list of available options and their purposes. </p> @@ -239,7 +239,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.3.3/gcc/Submodel-Options.html#Submodel-Options">manual</uri> +link="http://gcc.gnu.org/onlinedocs/gcc-4.4.4/gcc/Submodel-Options.html#Submodel-Options">manual</uri> to determine which one you should use for your system. </p> @@ -248,7 +248,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.3.3/gcc/Submodel-Options.html#Submodel-Options">architecture-specific +link="http://gcc.gnu.org/onlinedocs/gcc-4.4.4/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> @@ -274,7 +274,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.3.3/gcc/Optimize-Options.html#Optimize-Options">optimization +link="http://gcc.gnu.org/onlinedocs/gcc-4.4.4/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> @@ -420,7 +420,7 @@ <note> You should check the <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> +link="http://gcc.gnu.org/onlinedocs/gcc-4.4.4/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> @@ -441,7 +441,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.3.3/gcc/Optimize-Options.html#Optimize-Options">manual</uri> +link="http://gcc.gnu.org/onlinedocs/gcc-4.4.4/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, @@ -582,11 +582,11 @@ abusive</uri> ways of trying force Portage to do so. </p> -<p> +<warn> You <e>should not</e> try to force Portage to use per-package flags, as it is not in any way supported and will greatly complicate bug reports. Just set your flags in <path>/etc/make.conf</path> to be used on a system-wide basis. -</p> +</warn> </body> </section> @@ -603,7 +603,7 @@ <ul> <li> - The <uri link="http://gcc.gnu.org/onlinedocs/gcc-4.3.3/gcc/">GNU gcc + The <uri link="http://gcc.gnu.org/onlinedocs/gcc-4.4.4/gcc/">GNU gcc manual</uri> </li> <li>