[lkml]   [2004]   [Jul]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: GCC 3.4 and broken inlining.

    On Fri, 2004-07-09 at 14:51, Andi Kleen wrote:
    > Nigel Cunningham <> writes:

    I'm not sure what I wrote that you're replying to.

    > I think a better solution would be to apply the appended patch

    I'm going to be a pragmatist :> As long as it works. I do think that
    functions being declared inline when they can't be inlined is wrong, but
    there are more important things on which to spend my time.

    > And then just mark the function you know needs to be inlined
    > as __always_inline__. I did this on x86-64 for some functions
    > too that need to be always inlined (although using the attribute
    > directly because all x86-64 compilers support it)

    Should that be __always_inline (no final __ in the patch below, so far
    as I can see)?


    > P.S.: compiler.h seems to be not "gcc 4.0 safe". Probably that needs
    > to be fixed too.




    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: 2005-03-22 14:04    [W:0.019 / U:12.292 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site