> No idea. To me it sounds that -mincoming-stack-boundary=2 would allow to do
> -mstackrealign in those functions where it is necessary rather than in all.
That's not my reading of ix86_minimum_incoming_stack_boundary:
/* Prefer the one specified at command line. */
if (ix86_user_incoming_st
On Fri, Feb 19, 2016 at 7:50 PM, Eric Botcazou wrote:
>> Not sure - why doesn't mingw properly specify the default incoming
>> stack boundary?
>> If it does, why isn't there an issue elsewhere even on non-mingw if you use
>> -mincoming-stack-boundary=2?
>
> Wouldn't that pessimize over -mstackreal
> Not sure - why doesn't mingw properly specify the default incoming
> stack boundary?
> If it does, why isn't there an issue elsewhere even on non-mingw if you use
> -mincoming-stack-boundary=2?
Wouldn't that pessimize over -mstackrealign? That's my reading of the manual.
Note that the issue is
On Fri, Feb 19, 2016 at 12:50 PM, Eric Botcazou wrote:
> Any (global or platform) maintainer willing to approve this for GCC6?
> https://gcc.gnu.org/ml/gcc-patches/2015-12/msg01458.html
>
> We switched to SSE2 by default on Windows 32-bit at AdaCore and we ran into
> really nasty stability issue
> This is really Windows specific setting, so Windows maintainer should
> OK the patch.
Makes sense, both maintainers now CCed.
https://gcc.gnu.org/ml/gcc-patches/2015-12/msg01458.html
--
Eric Botcazou
On Mon, Jan 4, 2016 at 9:26 AM, Eric Botcazou wrote:
> https://gcc.gnu.org/ml/gcc-patches/2015-12/msg01458.html
>
> Thanks in advance.
This is really Windows specific setting, so Windows maintainer should
OK the patch.
Uros.
