From 3af64fd603e2f7aa8aed9f34f560c837ab89a319 Mon Sep 17 00:00:00 2001 From: Mark Mitchell Date: Thu, 15 Feb 2001 18:23:33 +0000 Subject: [PATCH] * invoke.texi (--param): Document. From-SVN: r39723 --- gcc/ChangeLog | 4 ++++ gcc/invoke.texi | 19 +++++++++++++++++++ 2 files changed, 23 insertions(+) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index fbe44cd79c1..c27b695ab7b 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,7 @@ +2001-02-15 Mark Mitchell + + * invoke.texi (--param): Document. + Thu Feb 15 15:16:38 2001 Alexandre Oliva * config/sh/sh.h (BOOL_TYPE_SIZE): Don't define. diff --git a/gcc/invoke.texi b/gcc/invoke.texi index 896d9f93bf5..302f97a4a7b 100644 --- a/gcc/invoke.texi +++ b/gcc/invoke.texi @@ -254,6 +254,7 @@ in the following sections. -fsingle-precision-constant -fssa @gol -fstrength-reduce -fstrict-aliasing -fthread-jumps -ftrapv @gol -funroll-all-loops -funroll-loops @gol +--param @var{name}=@var{value} -O -O0 -O1 -O2 -O3 -Os} @item Preprocessor Options @@ -3261,6 +3262,24 @@ of registers left over after register allocation. This optimization will most benefit processors with lots of registers. It can, however, make debugging impossible, since variables will no longer stay in a ``home register''. + +@item --param @var{name}=@var{value} +In some places, GCC uses various constants to control the amount of +optimization that is done. For example, GCC will not inline functions +that contain more that a certain number of instructions. You can +control some of these constants on the command-line using the +@samp{--param} option. + +In each case, the @var{value} is a integer. The allowable choices for +@var{name} are given in the following table: + +@table @gcctabopt +@item max-inline-insns +If an function contains more than this many instructions, it +will not be inlined. This option is precisely equivalent to +@samp{-finline-limit}. +@end table + @end table @node Preprocessor Options