Re: Status of CONFIG_FORCED_INLINING?
- From: Roland Dreier <rdreier@xxxxxxxxx>
- Date: Thu, 24 May 2007 10:14:41 -0700
A function only belongs into a header file if we always want it inlined,
otherwise it belongs into a C file.
Again, why? Why don't we trust the compiler to decide if a function
should be inlined or not, even if the definition happens to be in a .h
file?
It seems like a perfectly valid optimization for the compiler to only
emit code once for a function and then call it where it is used, even
if that function happens to be defined in a .h file.
- R.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: Status of CONFIG_FORCED_INLINING?
- From: Adrian Bunk
- Re: Status of CONFIG_FORCED_INLINING?
- From: Rob Landley
- Re: Status of CONFIG_FORCED_INLINING?
- References:
- Status of CONFIG_FORCED_INLINING?
- From: Rob Landley
- Re: Status of CONFIG_FORCED_INLINING?
- From: Arjan van de Ven
- Re: Status of CONFIG_FORCED_INLINING?
- From: Adrian Bunk
- Re: Status of CONFIG_FORCED_INLINING?
- From: Roland Dreier
- Re: Status of CONFIG_FORCED_INLINING?
- From: Adrian Bunk
- Status of CONFIG_FORCED_INLINING?
- Prev by Date: Re: [2/3] 2.6.22-rc2: known regressions v2
- Next by Date: RE: [PATCH] [scsi] Remove __GFP_DMA
- Previous by thread: Re: Status of CONFIG_FORCED_INLINING?
- Next by thread: Re: Status of CONFIG_FORCED_INLINING?
- Index(es):
Relevant Pages
|