Slashdot Mirror

← Back to Stories (view on slashdot.org)

GCC 4.3.0 Exposes a Kernel Bug

Posted by kdawson on from the my-flag-boy-told-your-flag-boy dept.

ohxten sends news from earlier this month that GCC 4.3.0's new behavior of not clearing the direction flag before a string operation on x86 systems poses problems with kernels — such as Linux and BSD — that do not clear the direction flag before a signal handler is called, despite the ABI specification.

7 of 256 comments (clear)

  1. Yep, by EkriirkE · · Score: 5, Funny

    That's what happens when you don't clear that STD...

    --
    from 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
    to 45 2F 6E 40 3C DF 10 71 4E 41 DF AA 25 7D 31 3F
  2. Kernel bug by Harmonious+Botch · · Score: 4, Funny

    Better than a general fault.

  3. EVERYBODY PANIC!!! by Anonymous Coward · · Score: 5, Funny

    GCC 4.3.0's new behavior of not clearing the direction flag before a string operation on x86 systems poses problems with kernels -- such as Linux and BSD -- that do not clear the direction flag before a signal handler is called, despite the ABI specification.

    Oh my GOD! If this is true, that means- that means-- it... the-

    Uh, what does it mean exactly?

    1. Re:EVERYBODY PANIC!!! by Anonymous Coward · · Score: 5, Funny

      I'm sorry, I'll need a car analogy on that one.

  4. Re:[LWN subscriber-only content] by gambolt · · Score: 5, Funny

    Information wants to be free. Bandwidth wants to cost money.

  5. Re:so what by larry+bagina · · Score: 5, Funny

    at least nothing of value is affected.

    --
    Do you even lift?

    These aren't the 'roids you're looking for.

  6. Re:so what by xaxa · · Score: 4, Funny

    It depends, the US Fuckton is less than a metric assload, but the Imperial Fuckton, previously used in the UK, was more.

    NB The use of 'assload' without the 'metric' qualifier is discouraged, the customary US assload being a much greater mass.