lkml.org 
[lkml]   [2004]   [Jul]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: GCC 3.4 and broken inlining.
    From
    Date
    On Jul  9, 2004, Andi Kleen <ak@muc.de> wrote:

    > Nigel Cunningham <ncunningham@linuxmail.org> writes:

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

    Agreed.

    > And then just mark the function you know needs to be inlined
    > as __always_inline__.

    It's probably a good idea to define such functions as `extern inline'
    (another GCC extension), such that a definition of the function is
    never emitted, and you get a linker error if the compiler somehow
    fails to emit an error on a failure to inline the function.

    --
    Alexandre Oliva http://www.ic.unicamp.br/~oliva/
    Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
    Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}
    -
    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: 2005-03-22 14:04    [W:0.031 / U:0.156 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site