On Apr 02 2021, Martin Sebor wrote:
> One way to confirm this hypothesis might be to explicitly
> initialize the limit member in the ctor even the argument is
> ALLOCA_OK and see if the warning goes away.
Yes, it does.
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 757
On 4/2/21 9:40 AM, Jan Hubicka wrote:
This breaks bootstrap on riscv64:
In function ‘alloca_type_and_limit alloca_call_type(range_query&, gimple*, bool
’,
inlined from ‘virtual unsigned int pass_walloca::execute(function*)’ at
../../gcc/gimple-ssa-warn-alloca.c:295:25:
../../gcc/gimple-ss
> This breaks bootstrap on riscv64:
>
> In function ‘alloca_type_and_limit alloca_call_type(range_query&, gimple*,
> bool ’,
> inlined from ‘virtual unsigned int pass_walloca::execute(function*)’ at
> ../../gcc/gimple-ssa-warn-alloca.c:295:25:
> ../../gcc/gimple-ssa-warn-alloca.c:206:13: err
On Mär 31 2021, Jan Hubicka via Gcc-cvs wrote:
> https://gcc.gnu.org/g:e7fd3b783238d034018443e43a58ff87908b4db6
>
> commit r11-7940-ge7fd3b783238d034018443e43a58ff87908b4db6
> Author: Jan Hubicka
> Date: Wed Mar 31 22:44:20 2021 +0200
>
> Make USES_COMDAT_LOCAL CIF_FINAL_NORMAL
>
>
