1 |
nightmorph 09/06/26 03:33:21 |
2 |
|
3 |
Modified: gcc-optimization.xml |
4 |
Log: |
5 |
update options and links to gcc 4.3 |
6 |
|
7 |
Revision Changes Path |
8 |
1.15 xml/htdocs/doc/en/gcc-optimization.xml |
9 |
|
10 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-optimization.xml?rev=1.15&view=markup |
11 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-optimization.xml?rev=1.15&content-type=text/plain |
12 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-optimization.xml?r1=1.14&r2=1.15 |
13 |
|
14 |
Index: gcc-optimization.xml |
15 |
=================================================================== |
16 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-optimization.xml,v |
17 |
retrieving revision 1.14 |
18 |
retrieving revision 1.15 |
19 |
diff -u -r1.14 -r1.15 |
20 |
--- gcc-optimization.xml 22 Jul 2008 05:56:05 -0000 1.14 |
21 |
+++ gcc-optimization.xml 26 Jun 2009 03:33:21 -0000 1.15 |
22 |
@@ -1,6 +1,6 @@ |
23 |
<?xml version='1.0' encoding='UTF-8'?> |
24 |
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
25 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-optimization.xml,v 1.14 2008/07/22 05:56:05 nightmorph Exp $ --> |
26 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-optimization.xml,v 1.15 2009/06/26 03:33:21 nightmorph Exp $ --> |
27 |
|
28 |
<guide link="/doc/en/gcc-optimization.xml"> |
29 |
<title>Compilation Optimization Guide</title> |
30 |
@@ -19,8 +19,8 @@ |
31 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
32 |
<license/> |
33 |
|
34 |
-<version>1.9</version> |
35 |
-<date>2008-07-21</date> |
36 |
+<version>1.10</version> |
37 |
+<date>2009-06-25</date> |
38 |
|
39 |
<chapter> |
40 |
<title>Introduction</title> |
41 |
@@ -39,7 +39,7 @@ |
42 |
They can be used to decrease the amount of debug messages for a program, |
43 |
increase error warning levels, and, of course, to optimize the code produced. |
44 |
The <uri |
45 |
-link="http://gcc.gnu.org/onlinedocs/gcc-4.1.2/gcc/Invoking-GCC.html#Invoking-GCC">GNU |
46 |
+link="http://gcc.gnu.org/onlinedocs/gcc-4.3.3/gcc/Invoking-GCC.html#Invoking-GCC">GNU |
47 |
gcc handbook</uri> maintains a complete list of available options and their |
48 |
purposes. |
49 |
</p> |
50 |
@@ -139,7 +139,7 @@ |
51 |
<note> |
52 |
Whenever you're not sure what a flag actually does, refer to the relevant |
53 |
chapter of the <uri |
54 |
-link="http://gcc.gnu.org/onlinedocs/gcc-4.1.2/gcc/Optimize-Options.html#Optimize-Options">gcc |
55 |
+link="http://gcc.gnu.org/onlinedocs/gcc-4.3.3/gcc/Optimize-Options.html#Optimize-Options">gcc |
56 |
manual</uri>. If you're still stumped, try Google, or check out the <c>gcc</c> |
57 |
<uri link="http://gcc.gnu.org/lists.html">mailing lists</uri>. |
58 |
</note> |
59 |
@@ -224,7 +224,7 @@ |
60 |
x86/x86-64) . . . but with a different flag name. Again, <c>gcc</c>'s behavior |
61 |
and flag naming just isn't consistent across architectures, so be sure to check |
62 |
the <c>gcc</c> <uri |
63 |
-link="http://gcc.gnu.org/onlinedocs/gcc-4.1.2/gcc/Submodel-Options.html#Submodel-Options">manual</uri> |
64 |
+link="http://gcc.gnu.org/onlinedocs/gcc-4.3.3/gcc/Submodel-Options.html#Submodel-Options">manual</uri> |
65 |
to determine which one you should use for your system. |
66 |
</p> |
67 |
|
68 |
@@ -233,7 +233,7 @@ |
69 |
read chapter 5 of the appropriate <uri link="/doc/en/handbook/">Gentoo |
70 |
Installation Handbook</uri> for your arch. Also, read the <c>gcc</c> manual's |
71 |
list of <uri |
72 |
-link="http://gcc.gnu.org/onlinedocs/gcc-4.1.2/gcc/Submodel-Options.html#Submodel-Options">architecture-specific |
73 |
+link="http://gcc.gnu.org/onlinedocs/gcc-4.3.3/gcc/Submodel-Options.html#Submodel-Options">architecture-specific |
74 |
options</uri>, as well as more detailed explanations about the differences |
75 |
between <c>-march</c>, <c>-mcpu</c>, and <c>-mtune</c>. |
76 |
</note> |
77 |
@@ -259,7 +259,7 @@ |
78 |
<p> |
79 |
With the exception of <c>-O0</c>, the <c>-O</c> settings each activate several |
80 |
additional flags, so be sure to read the gcc manual's chapter on <uri |
81 |
-link="http://gcc.gnu.org/onlinedocs/gcc-4.1.2/gcc/Optimize-Options.html#Optimize-Options">optimization |
82 |
+link="http://gcc.gnu.org/onlinedocs/gcc-4.3.3/gcc/Optimize-Options.html#Optimize-Options">optimization |
83 |
options</uri> to learn which flags are activated at each <c>-O</c> level, as |
84 |
well as some explanations as to what they do. |
85 |
</p> |
86 |
@@ -404,7 +404,7 @@ |
87 |
|
88 |
<note> |
89 |
You should check the <uri |
90 |
-link="http://gcc.gnu.org/onlinedocs/gcc-4.1.2/gcc/i386-and-x86_002d64-Options.html#i386-and-x86_002d64-Options">list</uri> |
91 |
+link="http://gcc.gnu.org/onlinedocs/gcc-4.3.3/gcc/i386-and-x86_002d64-Options.html#i386-and-x86_002d64-Options">list</uri> |
92 |
of x86 and x86-64-specific flags to see which of these instruction sets are |
93 |
activated by the proper CPU type flag. If an instruction is listed, then you |
94 |
don't need to specify it; it will be turned on by using the proper <c>-march</c> |
95 |
@@ -425,7 +425,7 @@ |
96 |
No, you only <e>think</e> you do because someone has convinced you that more |
97 |
flags are better. Aggressive flags will only hurt your applications when used |
98 |
system-wide. Even the <c>gcc</c> <uri |
99 |
-link="http://gcc.gnu.org/onlinedocs/gcc-4.1.2/gcc/Optimize-Options.html#Optimize-Options">manual</uri> |
100 |
+link="http://gcc.gnu.org/onlinedocs/gcc-4.3.3/gcc/Optimize-Options.html#Optimize-Options">manual</uri> |
101 |
says that using <c>-funroll-loops</c> and <c>-funroll-all-loops</c> makes code |
102 |
larger and run more slowly. Yet for some reason, these two flags, along with |
103 |
<c>-ffast-math</c>, <c>-fforce-mem</c>, <c>-fforce-addr</c>, and similar flags, |
104 |
@@ -587,7 +587,7 @@ |
105 |
|
106 |
<ul> |
107 |
<li> |
108 |
- The <uri link="http://gcc.gnu.org/onlinedocs/gcc-4.1.2/gcc/">GNU gcc |
109 |
+ The <uri link="http://gcc.gnu.org/onlinedocs/gcc-4.3.3/gcc/">GNU gcc |
110 |
manual</uri> |
111 |
</li> |
112 |
<li> |