[lkml]   [2007]   [Aug]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH] make atomic_t volatile on all architectures

    On Sun, 12 Aug 2007, Segher Boessenkool wrote:
    > Yeah. Compiler errors are more annoying though I dare say ;-)

    Actually, compile-time errors are fine, and easy to work around. *Much*
    more annoying is when gcc actively generates subtly bad code. We've had
    use-after-free issues due to incorrect gcc liveness calculations etc, and
    inline asm has beeen one of the more common causes - exactly because the
    kernel is one of the few users (along with glibc) that uses it at all.

    Now *those* are hard to find - the code works most of the time, but the
    compiler has inserted a really subtle race condition into the code
    (deallocated a local stack entry before last use). We had that with our
    semaphore code at some point.

    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-08-12 20:15    [W:0.019 / U:36.228 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site