On Mon, Jul 6, 2015 at 6:44 AM, Ingo Molnar <mi...@kernel.org> wrote:
>
> So looking at this I question the choice of -mpreferred-stack-boundary=3. Why
> not
> do -mpreferred-stack-boundary=2?
It wouldn't make sense anyway - it would only make code worse (if it
worked) and not any better.
The reason the "=3" value is good is because 8-byte alignment is the
"natural" alignment - it's what you get with a normal call sequence,
simply because the return address is 8 bytes in size.
That means that with "=3" you don't get extra code to align the stack
for the simple functions that don't need a frame.
Anything smaller than 3 wouldn't help even if it worked, because none
of the normal stack operations (pushing/popping registers to
save/restore them) would be any smaller anyway.
But bigger values than 3 result in the compiler having to generate
extra stack adjustments just to align the stack after a call that very
naturally mis-aligned it. And it doesn't help anyway, since in the
kernel we don't put stuff on the stack that needs bigger alignment
(of, the fxsave buffer is a counter-example, but it's a very odd one
that we _shouldn't_ have put on the stack).
Linus
--
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/
