[lkml]   [2007]   [May]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: Status of CONFIG_FORCED_INLINING?
    On Wed, 23 May 2007, 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.

    i hate to be in the middle of one of these again, but i think i
    initiated this topic way back when when i (like rob landley) asked why
    that config option was still around when it's been listed for deletion
    for a year.

    regardless of its good or bad points, one way or the other, something
    should be updated.

    Robert P. J. Day
    Linux Consulting, Training and Annoying Kernel Pedantry
    Waterloo, Ontario, CANADA
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2007-05-24 14:43    [W:0.034 / U:113.904 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site