lkml.org 
[lkml]   [2007]   [May]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: Status of CONFIG_FORCED_INLINING?
    On Wed, May 23, 2007 at 02:28:56PM -0700, Roland Dreier wrote:
    > > - every static function in a header file must be __always_inline
    >
    > Why? Why does it matter whether a function is defined in a .h file or
    > a .c file? Can't the compiler decide better than we can whether
    > something should be inlined or not?
    >
    > Your argument seems to imply that we should never use the inline
    > keyword at all.

    A function only belongs into a header file if we always want it inlined,
    otherwise it belongs into a C file.

    > - R.

    cu
    Adrian

    --

    "Is there not promise of rain?" Ling Tan asked suddenly out
    of the darkness. There had been need of rain for many days.
    "Only a promise," Lao Er said.
    Pearl S. Buck - Dragon Seed

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2007-05-24 19:13    [W:0.020 / U:29.680 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site