This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: max-inline-insns (was: [3.4/mainline] Tweak inlining limits)


Richard Henderson <rth@redhat.com> writes:

> On Thu, Jan 22, 2004 at 03:44:56PM -0500, Ian Lance Taylor wrote:
> > If old --param names are going to cause compiler failure, then I think
> > parameters should be deprecated for a release before being removed,
> > just as with other user visible features.
> 
> They poke compiler internals.  Compiler internals change without notice.
> I don't see what purpose this would serve.

OK, I propose the appended patch to the documentation.

Tested by running `make all'.

Ian


2004-01-22  Ian Lance Taylor  <ian@wasabisystems.com>

	* doc/invoke.texi (Optimize Options): Note that --param arguments
	are subject to change without notice.


Index: invoke.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/doc/invoke.texi,v
retrieving revision 1.394
diff -p -u -r1.394 invoke.texi
--- invoke.texi	18 Jan 2004 11:57:12 -0000	1.394
+++ invoke.texi	23 Jan 2004 00:42:45 -0000
@@ -4659,6 +4659,10 @@ that contain more that a certain number 
 control some of these constants on the command-line using the
 @option{--param} option.
 
+The names of specific parameters, and the meaning of the values, are
+tied to the internals of the compiler, and are subject to change
+without notice in future releases.
+
 In each case, the @var{value} is an integer.  The allowable choices for
 @var{name} are given in the following table:
 


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]