This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
PATCH for Re: 3.0.1 performance
- To: <gcc-patches at gcc dot gnu dot org>
- Subject: PATCH for Re: 3.0.1 performance
- From: Gerald Pfeifer <pfeifer at dbai dot tuwien dot ac dot at>
- Date: Fri, 17 Aug 2001 21:16:05 +0200 (CEST)
- cc: Phil Edwards <pedwards at disaster dot jaj dot com>, Kurt Garloff <kurt at garloff dot de>, <gcc at gcc dot gnu dot org>
On Fri, 17 Aug 2001, Phil Edwards wrote:
> The current limit /is/ 600, IIRC. Perhaps the docs did not get updated
Right. I just installed the following on mainline and will move to the
branch in a minute...
2001-08-17 Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
* doc/invoke.texi (Optimize Options): The default for
-finline-limit is 600.
Index: doc/invoke.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/doc/invoke.texi,v
retrieving revision 1.44
diff -u -3 -p -r1.44 invoke.texi
--- invoke.texi 2001/08/03 01:19:20 1.44
+++ invoke.texi 2001/08/17 19:13:47
@@ -3310,7 +3310,8 @@ allows the control of this limit for fun
inline (ie marked with the inline keyword or defined within the class
definition in c++). @var{n} is the size of functions that can be inlined in
number of pseudo instructions (not counting parameter handling). The default
-value of @var{n} is 10000. Increasing this value can result in more inlined code at
+value of @var{n} is 600.
+Increasing this value can result in more inlined code at
the cost of compilation time and memory consumption. Decreasing usually makes
the compilation faster and less code will be inlined (which presumably
means slower programs). This option is particularly useful for programs that