linux-2.2.1-ac3 and egcs-19990131

[Richard Henderson]

On Mon, Feb 08, 1999 at 06:15:11PM -0700, Jeffrey A Law wrote:
> Seems reasonable.  We probably need a minor tweak to the docs for
> either inline functions or computed gotos, or possibly both.

Committed.  I've also added the following tweek.


r~



Index: extend.texi
===================================================================
RCS file: /egcs/carton/cvsfiles/egcs/gcc/extend.texi,v
retrieving revision 1.22
diff -c -p -d -r1.22 extend.texi
*** extend.texi	1999/01/04 11:56:18	1.22
--- extend.texi	1999/02/09 05:59:40
*************** inc (int *a)
*** 2258,2267 ****
  
  (If you are writing a header file to be included in ANSI C programs, write
  @code{__inline__} instead of @code{inline}.  @xref{Alternate Keywords}.)
- 
  You can also make all ``simple enough'' functions inline with the option
! @samp{-finline-functions}.  Note that certain usages in a function
! definition can make it unsuitable for inline substitution.
  
  Note that in C and Objective C, unlike C++, the @code{inline} keyword
  does not affect the linkage of the function.
--- 2258,2273 ----
  
  (If you are writing a header file to be included in ANSI C programs, write
  @code{__inline__} instead of @code{inline}.  @xref{Alternate Keywords}.)
  You can also make all ``simple enough'' functions inline with the option
! @samp{-finline-functions}. 
! 
! Note that certain usages in a function definition can make it unsuitable
! for inline substitution.  Among these usages are: use of varargs, use of
! alloca, use of variable sized data types (@pxref{Variable Length}),
! use of computed goto (@pxref{Labels as Values}), use of nonlocal goto,
! and nested functions (@pxref{Nested Functions}).  Using @samp{-Winline}
! will warn when a function marked @code{inline} could not be substituted,
! and will give the reason for the failure.
  
  Note that in C and Objective C, unlike C++, the @code{inline} keyword
  does not affect the linkage of the function.