Gentoo Archives: gentoo-doc-cvs

From: "Xavier Neys (neysx)" <neysx@g.o>
To: gentoo-doc-cvs@l.g.o
Subject: [gentoo-doc-cvs] gentoo commit in xml/htdocs/doc/en: gcc-optimization.xml
Date: Mon, 19 Oct 2009 16:16:38
Message-Id: E1MzuuS-0007w4-Mk@stork.gentoo.org
1 neysx 09/10/19 16:16:36
2
3 Modified: gcc-optimization.xml
4 Log:
5 #289741 mention -pipe uses more memory
6
7 Revision Changes Path
8 1.17 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.17&view=markup
11 plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-optimization.xml?rev=1.17&content-type=text/plain
12 diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-optimization.xml?r1=1.16&r2=1.17
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.16
18 retrieving revision 1.17
19 diff -u -r1.16 -r1.17
20 --- gcc-optimization.xml 19 Jul 2009 02:05:08 -0000 1.16
21 +++ gcc-optimization.xml 19 Oct 2009 16:16:36 -0000 1.17
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.16 2009/07/19 02:05:08 nightmorph Exp $ -->
26 +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-optimization.xml,v 1.17 2009/10/19 16:16:36 neysx 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.11</version>
35 -<date>2009-07-18</date>
36 +<version>1.12</version>
37 +<date>2009-10-19</date>
38
39 <chapter>
40 <title>Introduction</title>
41 @@ -340,10 +340,11 @@
42 <body>
43
44 <p>
45 -A fun, safe flag to use is <c>-pipe</c>. This flag actually has no effect on the
46 +A common flag is <c>-pipe</c>. This flag actually has no effect on the
47 generated code, but it makes the compilation process faster. It tells the
48 compiler to use pipes instead of temporary files during the different stages of
49 -compilation.
50 +compilation, which uses more memory. On systems with low memory, gcc might get
51 +killed. In that case, do not use this flag.
52 </p>
53
54 </body>