cvs commit: src/sys/kern init_main.c kern_malloc.c md5c.c subr_autoconf.c subr_mbuf.c subr_prf.c tty_subr.c vfs_cluster.c vfs_subr.c

Alan L. Cox alc at imimic.com
Tue Jul 22 11:54:37 PDT 2003


Steve Kargl wrote:
> 
> On Tue, Jul 22, 2003 at 11:29:01AM +0000, Bosko Milekic wrote:
> >
> >   Is there a way to force GCC to inline them, despite what it thinks?
> 
> info gcc
> 
> `-finline-limit=N'
>      By default, gcc limits the size of functions that can be inlined.
>      This flag allows the control of this limit for functions that are
>      explicitly marked as inline (i.e., marked with the inline keyword
>      or defined within the class definition in c++).  N is the size of
>      functions that can be inlined in number of pseudo instructions
>      (not counting parameter handling).  The default value of N is 600.
>      Increasing this value can result in more inlined code at the cost
>      of compilation time and memory consumption.  Decreasing usually
> 

There is another way.  The following example illustrates its use.

static int    vm_object_backing_scan(vm_object_t object, int op)
__attribute__((always_inline));

Regards,
Alan


More information about the cvs-all mailing list