On 22/11/2019 11:52, Andrew Pinski wrote:
> I should say that you need all three options to prevent the code motion from
> happening:
> -fno-tree-loop-im -fno-tree-pre -fno-gcse
>
> -fno-tree-ch prevents the code motion from happening too but only on
> accident; in that all three of the code m
t: Re: [EXT] High stack usage due ftree-ch
>Thanks for the information, at least for the specific snippet it seems that
> both -fno-tree-loop-im and -fno-tree-pre are the ones generating most
> spilling.
That is because the code motion is happening at the RTL level: -fno-gcse is the
one y
oking for.
From: Adhemerval Zanella
Sent: Friday, November 22, 2019 6:41 AM
To: Andrew Pinski; Arnd Bergmann
Cc: Linaro Toolchain Mailman List
Subject: Re: [EXT] High stack usage due ftree-ch
On 22/11/2019 11:38, Andrew Pinski wrote:
>> It is enabled in all optimization lev
> To: Arnd Bergmann
> Cc: Linaro Toolchain Mailman List
> Subject: [EXT] High stack usage due ftree-ch
>
> External Email
>
> --
> Hi Arnd,
>
> I took a look on the stack usage issue in the ker
_
From: linaro-toolchain on behalf of
Adhemerval Zanella
Sent: Friday, November 22, 2019 5:40 AM
To: Arnd Bergmann
Cc: Linaro Toolchain Mailman List
Subject: [EXT] High stack usage due ftree-ch
External Email
--
Hi Arnd,
I took a l
n. It has some heurstics but those are not always good.
Thanks,
Andrew Pinski
From: linaro-toolchain on behalf of
Adhemerval Zanella
Sent: Friday, November 22, 2019 5:40 AM
To: Arnd Bergmann
Cc: Linaro Toolchain Mailman List
Subject: [EXT] High stack usage
