[gentoo-commits] gentoo commit in xml/htdocs/doc/en: gcc-optimization.xml

[gentoo-commits] gentoo commit in xml/htdocs/doc/en: gcc-optimization.xml

[Josh Saddler (nightmorph)]

nightmorph    07/11/10 01:03:47

  Log:
  
-- 
gentoo-commits@gentoo.org mailing list

[gentoo-commits] gentoo commit in xml/htdocs/doc/en: gcc-optimization.xml

[Josh Saddler (nightmorph)]

nightmorph    07/11/10 01:18:15

  Log:
  
-- 
gentoo-commits@gentoo.org mailing list

[gentoo-commits] gentoo commit in xml/htdocs/doc/en: gcc-optimization.xml

[Joshua Saddler (nightmorph)]

nightmorph    08/07/22 05:56:05

  Log:
  

[gentoo-commits] gentoo commit in xml/htdocs/doc/en: gcc-optimization.xml

[Joshua Saddler (nightmorph)]

nightmorph    09/06/26 03:33:22

  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>

[gentoo-commits] gentoo commit in xml/htdocs/doc/en: gcc-optimization.xml

[Joshua Saddler (nightmorph)]

nightmorph    09/07/19 02:05:08

  Modified:             gcc-optimization.xml
  Log:
  add some information about -march=native

Revision  Changes    Path
1.16                 xml/htdocs/doc/en/gcc-optimization.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-optimization.xml?rev=1.16&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-optimization.xml?rev=1.16&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-optimization.xml?r1=1.15&r2=1.16

Index: gcc-optimization.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-optimization.xml,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- gcc-optimization.xml	26 Jun 2009 03:33:21 -0000	1.15
+++ gcc-optimization.xml	19 Jul 2009 02:05:08 -0000	1.16
@@ -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.15 2009/06/26 03:33:21 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-optimization.xml,v 1.16 2009/07/19 02:05:08 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.10</version>
-<date>2009-06-25</date>
+<version>1.11</version>
+<date>2009-07-18</date>
 
 <chapter>
 <title>Introduction</title>
@@ -195,6 +195,21 @@
 CXXFLAGS="${CFLAGS}"
 </pre>
 
+<p>
+If you still aren't sure what kind of CPU you have, you may just want to use
+<c>-march=native</c>. When this flag is used, GCC will detect your processor and
+automatically set appropriate flags for it. <brite>However, this should not be
+used if you intend to compile packages for a different CPU!</brite>
+</p>
+
+<p>
+So if you're compiling packages on one computer, but intend to run them on a
+different computer (such as when using a fast computer to build for an older,
+slower machine), then <e>do not</e> use <c>-march=native</c>. "Native" means
+that the code produced will run <e>only</e> on that type of CPU. The
+applications built with <c>-march=native</c> on an AMD Athlon 64 CPU will not be
+able to run on an old VIA C3 CPU.
+</p>
 
 <p>
 Also available are the <c>-mtune</c> and <c>-mcpu</c> flags. These flags are

[gentoo-commits] gentoo commit in xml/htdocs/doc/en: gcc-optimization.xml

[Xavier Neys (neysx)]

neysx       09/10/19 16:16:37

  Modified:             gcc-optimization.xml
  Log:
  #289741 mention -pipe uses more memory

Revision  Changes    Path
1.17                 xml/htdocs/doc/en/gcc-optimization.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-optimization.xml?rev=1.17&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-optimization.xml?rev=1.17&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-optimization.xml?r1=1.16&r2=1.17

Index: gcc-optimization.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-optimization.xml,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- gcc-optimization.xml	19 Jul 2009 02:05:08 -0000	1.16
+++ gcc-optimization.xml	19 Oct 2009 16:16:36 -0000	1.17
@@ -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.16 2009/07/19 02:05:08 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-optimization.xml,v 1.17 2009/10/19 16:16:36 neysx 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.11</version>
-<date>2009-07-18</date>
+<version>1.12</version>
+<date>2009-10-19</date>
 
 <chapter>
 <title>Introduction</title>
@@ -340,10 +340,11 @@
 <body>
 
 <p>
-A fun, safe flag to use is <c>-pipe</c>. This flag actually has no effect on the
+A common flag is <c>-pipe</c>. This flag actually has no effect on the
 generated code, but it makes the compilation process faster. It tells the
 compiler to use pipes instead of temporary files during the different stages of
-compilation.
+compilation, which uses more memory. On systems with low memory, gcc might get
+killed. In that case, do not use this flag.
 </p>
 
 </body>

[gentoo-commits] gentoo commit in xml/htdocs/doc/en: gcc-optimization.xml

[Joshua Saddler (nightmorph)]

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="nightmorph@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>

[gentoo-commits] gentoo commit in xml/htdocs/doc/en: gcc-optimization.xml

[Sven Vermeulen (swift)]

swift       12/04/22 10:37:32

  Modified:             gcc-optimization.xml
  Log:
  Fix bug #412853 - Refer to the package.env location for per-package CFLAGS

Revision  Changes    Path
1.19                 xml/htdocs/doc/en/gcc-optimization.xml

file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/gcc-optimization.xml?rev=1.19&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/gcc-optimization.xml?rev=1.19&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/gcc-optimization.xml?r1=1.18&r2=1.19

Index: gcc-optimization.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-optimization.xml,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- gcc-optimization.xml	27 Jul 2010 00:24:29 -0000	1.18
+++ gcc-optimization.xml	22 Apr 2012 10:37:32 -0000	1.19
@@ -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.18 2010/07/27 00:24:29 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-optimization.xml,v 1.19 2012/04/22 10:37:32 swift Exp $ -->
 
 <guide>
 <title>Compilation Optimization Guide</title>
@@ -19,8 +19,8 @@
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 <license/>
 
-<version>2</version>
-<date>2010-07-26</date>
+<version>3</version>
+<date>2012-04-22</date>
 
 <chapter>
 <title>Introduction</title>
@@ -575,19 +575,19 @@
 <title>Can I use per-package flags?</title>
 <body>
 
-<p>
-There is no supported method for using CFLAGS or other variables on a
-per-package basis, though there are a few <uri
-link="http://forums.gentoo.org/viewtopic-p-3832057.html#3832057">rather
-abusive</uri> ways of trying force Portage to do so.
-</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.
+Using per-package flags complicates debugging and support. Make sure you mention
+in your bug reports if you make use of this feature and what the changes are you
+made.
 </warn>
 
+<p>
+Information on how to use per-package environment variables (including CFLAGS)
+is described in the <uri
+link="/doc/en/handbook/handbook-amd64.xml?part=3&amp;chap=6#doc_chap2">Gentoo
+Handbook, "Per-Package Environment Variables"</uri>.
+</p>
+
 </body>
 </section>
 </chapter>

[gentoo-commits] gentoo commit in xml/htdocs/doc/en: gcc-optimization.xml

[Sven Vermeulen (swift)]

swift       12/12/25 18:19:47

  Modified:             gcc-optimization.xml
  Log:
  Fix bug #448456 - Remove link to Acovea stuff, is not maintained nor available anymore. Thanks to Francesco Turco for reporting.

Revision  Changes    Path
1.21                 xml/htdocs/doc/en/gcc-optimization.xml

file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/gcc-optimization.xml?rev=1.21&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/gcc-optimization.xml?rev=1.21&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/gcc-optimization.xml?r1=1.20&r2=1.21

Index: gcc-optimization.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-optimization.xml,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -r1.20 -r1.21
--- gcc-optimization.xml	24 Jul 2012 12:12:51 -0000	1.20
+++ gcc-optimization.xml	25 Dec 2012 18:19:47 -0000	1.21
@@ -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.20 2012/07/24 12:12:51 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-optimization.xml,v 1.21 2012/12/25 18:19:47 swift Exp $ -->
 
 <guide>
 <title>Compilation Optimization Guide</title>
@@ -19,8 +19,8 @@
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 <license/>
 
-<version>4</version>
-<date>2012-04-27</date>
+<version>5</version>
+<date>2012-12-25</date>
 
 <chapter>
 <title>Introduction</title>
@@ -378,10 +378,6 @@
 <c>-fomit-frame-pointer</c> already does the job properly. Furthermore,
 <c>-momit-leaf-frame-pointer</c> has been shown to negatively impact code
 performance.
-<!--
-source for this info:
-http://www.coyotegulch.com/products/acovea/aco5p4gcc40.html
--->
 </impo>
 
 </body>
@@ -612,13 +608,6 @@
   </li>
   <li><c>man make.conf</c></li>
   <li><uri link="http://en.wikipedia.org">Wikipedia</uri></li>
-  <li>
-    <uri link="http://www.coyotegulch.com/products/acovea/">Acovea</uri>, a
-    benchmarking and test suite that can be useful for determining how different
-    compiler flags interact and affect generated code, though its code
-    suggestions are not appropriate for system-wide use. It is available in
-    Portage: <c>emerge acovea</c>.
-  </li>
   <li>The <uri link="http://forums.gentoo.org">Gentoo Forums</uri></li>
 </ul>