* Peter Zijlstra <pet...@infradead.org> wrote:
> > This is what we are going to return. But note that -20(%ebp) was not
> > initialized if TIF_NOTIFY_RESUME was already set, "jc .L2" skips .L5
> > above. IOW, in this case we seem to return a random value from stack.
>
> I think you're quite right, and I can confirm I can reproduce this with
> gcc-4.8.1 and Wu's .config:
>
> [...]
>
> Once I force a x86_64 build using the 'same' config it goes away and
> generates 'sensible' code again [...]
So this at least opens up the possibility that we can create a not too
painful quirk and only use the 'asm goto' optimization tricks on 64-bit
kernels?
Thanks,
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
