> Of course, the situation is particularly bad on s390, because every
> function call needs at least 96 bytes on the stack (due to the register
> save areas required by our ABI).
How is this different from sparc64?
Sparc64 even eats 192 bytes per function call, minimum. Sibling call
optimization in current GCC helps, but it is still an issue.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/