1 |
nightmorph 10/07/27 00:24:29 |
2 |
|
3 |
Modified: gcc-optimization.xml |
4 |
Log: |
5 |
Update gcc docs, fix some basic GuideXML |
6 |
|
7 |
Revision Changes Path |
8 |
1.18 xml/htdocs/doc/en/gcc-optimization.xml |
9 |
|
10 |
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/gcc-optimization.xml?rev=1.18&view=markup |
11 |
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/gcc-optimization.xml?rev=1.18&content-type=text/plain |
12 |
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/gcc-optimization.xml?r1=1.17&r2=1.18 |
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.17 |
18 |
retrieving revision 1.18 |
19 |
diff -u -r1.17 -r1.18 |
20 |
--- gcc-optimization.xml 19 Oct 2009 16:16:36 -0000 1.17 |
21 |
+++ gcc-optimization.xml 27 Jul 2010 00:24:29 -0000 1.18 |
22 |
@@ -1,12 +1,12 @@ |
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.17 2009/10/19 16:16:36 neysx Exp $ --> |
26 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-optimization.xml,v 1.18 2010/07/27 00:24:29 nightmorph Exp $ --> |
27 |
|
28 |
-<guide link="/doc/en/gcc-optimization.xml"> |
29 |
+<guide> |
30 |
<title>Compilation Optimization Guide</title> |
31 |
|
32 |
<author title="Author"> |
33 |
- <mail link="nightmorph@g.o">Joshua Saddler</mail> |
34 |
+ <mail link="nightmorph"/> |
35 |
</author> |
36 |
|
37 |
<abstract> |
38 |
@@ -19,8 +19,8 @@ |
39 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
40 |
<license/> |
41 |
|
42 |
-<version>1.12</version> |
43 |
-<date>2009-10-19</date> |
44 |
+<version>2</version> |
45 |
+<date>2010-07-26</date> |
46 |
|
47 |
<chapter> |
48 |
<title>Introduction</title> |
49 |
@@ -39,7 +39,7 @@ |
50 |
They can be used to decrease the amount of debug messages for a program, |
51 |
increase error warning levels, and, of course, to optimize the code produced. |
52 |
The <uri |
53 |
-link="http://gcc.gnu.org/onlinedocs/gcc-4.3.3/gcc/Invoking-GCC.html#Invoking-GCC">GNU |
54 |
+link="http://gcc.gnu.org/onlinedocs/gcc-4.4.4/gcc/Invoking-GCC.html#Invoking-GCC">GNU |
55 |
gcc handbook</uri> maintains a complete list of available options and their |
56 |
purposes. |
57 |
</p> |
58 |
@@ -239,7 +239,7 @@ |
59 |
x86/x86-64) . . . but with a different flag name. Again, <c>gcc</c>'s behavior |
60 |
and flag naming just isn't consistent across architectures, so be sure to check |
61 |
the <c>gcc</c> <uri |
62 |
-link="http://gcc.gnu.org/onlinedocs/gcc-4.3.3/gcc/Submodel-Options.html#Submodel-Options">manual</uri> |
63 |
+link="http://gcc.gnu.org/onlinedocs/gcc-4.4.4/gcc/Submodel-Options.html#Submodel-Options">manual</uri> |
64 |
to determine which one you should use for your system. |
65 |
</p> |
66 |
|
67 |
@@ -248,7 +248,7 @@ |
68 |
read chapter 5 of the appropriate <uri link="/doc/en/handbook/">Gentoo |
69 |
Installation Handbook</uri> for your arch. Also, read the <c>gcc</c> manual's |
70 |
list of <uri |
71 |
-link="http://gcc.gnu.org/onlinedocs/gcc-4.3.3/gcc/Submodel-Options.html#Submodel-Options">architecture-specific |
72 |
+link="http://gcc.gnu.org/onlinedocs/gcc-4.4.4/gcc/Submodel-Options.html#Submodel-Options">architecture-specific |
73 |
options</uri>, as well as more detailed explanations about the differences |
74 |
between <c>-march</c>, <c>-mcpu</c>, and <c>-mtune</c>. |
75 |
</note> |
76 |
@@ -274,7 +274,7 @@ |
77 |
<p> |
78 |
With the exception of <c>-O0</c>, the <c>-O</c> settings each activate several |
79 |
additional flags, so be sure to read the gcc manual's chapter on <uri |
80 |
-link="http://gcc.gnu.org/onlinedocs/gcc-4.3.3/gcc/Optimize-Options.html#Optimize-Options">optimization |
81 |
+link="http://gcc.gnu.org/onlinedocs/gcc-4.4.4/gcc/Optimize-Options.html#Optimize-Options">optimization |
82 |
options</uri> to learn which flags are activated at each <c>-O</c> level, as |
83 |
well as some explanations as to what they do. |
84 |
</p> |
85 |
@@ -420,7 +420,7 @@ |
86 |
|
87 |
<note> |
88 |
You should check the <uri |
89 |
-link="http://gcc.gnu.org/onlinedocs/gcc-4.3.3/gcc/i386-and-x86_002d64-Options.html#i386-and-x86_002d64-Options">list</uri> |
90 |
+link="http://gcc.gnu.org/onlinedocs/gcc-4.4.4/gcc/i386-and-x86_002d64-Options.html#i386-and-x86_002d64-Options">list</uri> |
91 |
of x86 and x86-64-specific flags to see which of these instruction sets are |
92 |
activated by the proper CPU type flag. If an instruction is listed, then you |
93 |
don't need to specify it; it will be turned on by using the proper <c>-march</c> |
94 |
@@ -441,7 +441,7 @@ |
95 |
No, you only <e>think</e> you do because someone has convinced you that more |
96 |
flags are better. Aggressive flags will only hurt your applications when used |
97 |
system-wide. Even the <c>gcc</c> <uri |
98 |
-link="http://gcc.gnu.org/onlinedocs/gcc-4.3.3/gcc/Optimize-Options.html#Optimize-Options">manual</uri> |
99 |
+link="http://gcc.gnu.org/onlinedocs/gcc-4.4.4/gcc/Optimize-Options.html#Optimize-Options">manual</uri> |
100 |
says that using <c>-funroll-loops</c> and <c>-funroll-all-loops</c> makes code |
101 |
larger and run more slowly. Yet for some reason, these two flags, along with |
102 |
<c>-ffast-math</c>, <c>-fforce-mem</c>, <c>-fforce-addr</c>, and similar flags, |
103 |
@@ -582,11 +582,11 @@ |
104 |
abusive</uri> ways of trying force Portage to do so. |
105 |
</p> |
106 |
|
107 |
-<p> |
108 |
+<warn> |
109 |
You <e>should not</e> try to force Portage to use per-package flags, as it is |
110 |
not in any way supported and will greatly complicate bug reports. Just set your |
111 |
flags in <path>/etc/make.conf</path> to be used on a system-wide basis. |
112 |
-</p> |
113 |
+</warn> |
114 |
|
115 |
</body> |
116 |
</section> |
117 |
@@ -603,7 +603,7 @@ |
118 |
|
119 |
<ul> |
120 |
<li> |
121 |
- The <uri link="http://gcc.gnu.org/onlinedocs/gcc-4.3.3/gcc/">GNU gcc |
122 |
+ The <uri link="http://gcc.gnu.org/onlinedocs/gcc-4.4.4/gcc/">GNU gcc |
123 |
manual</uri> |
124 |
</li> |
125 |
<li> |