Re: [PATCH] Initialize a variable due to -Wmaybe-uninitialized.

2019-11-21 Thread Andreas Schwab
On Nov 21 2019, Palmer Dabbelt wrote: > It's always initialized: the only path by which riscv_classify_address() > doesn't initialize it is on an error, That is not true. Only if GET_CODE (x) == LO_SUM, but then it is only accessed if addr.type is ADDRESS_LO_SUM, which is equivalent. Andreas.

Re: [PATCH] Initialize a variable due to -Wmaybe-uninitialized.

2019-11-21 Thread Palmer Dabbelt via gcc-patches
On Mon, 18 Nov 2019 09:58:19 PST (-0800), l...@redhat.com wrote: On 11/18/19 6:17 AM, Martin Liška wrote: Hi. The patch is about yet another bootstrap -Wmaybe-uninitialized warning. I've just tested that on risv64 cross compiler with latest trunk. Ready to be installed? Thanks, Martin gcc/Cha

Re: [PATCH] Initialize a variable due to -Wmaybe-uninitialized.

2019-11-19 Thread Andreas Schwab
On Nov 18 2019, Jeff Law wrote: > On 11/18/19 6:17 AM, Martin Liška wrote: >> Hi. >> >> The patch is about yet another bootstrap -Wmaybe-uninitialized warning. >> I've just tested that on risv64 cross compiler with latest trunk. >> >> Ready to be installed? >> Thanks, >> Martin >> >> gcc/Change

Re: [PATCH] Initialize a variable due to -Wmaybe-uninitialized.

2019-11-18 Thread Jeff Law
On 11/18/19 6:17 AM, Martin Liška wrote: > Hi. > > The patch is about yet another bootstrap -Wmaybe-uninitialized warning. > I've just tested that on risv64 cross compiler with latest trunk. > > Ready to be installed? > Thanks, > Martin > > gcc/ChangeLog: > > 2019-11-18  Martin Liska  > >