Re: disable -Warray-bounds in libgo (PR 101374)

2021-07-13 Thread Dimitar Dimitrov
On Fri, Jul 09, 2021 at 08:16:24AM +0200, Richard Biener via Gcc-patches wrote: > On Thu, Jul 8, 2021 at 8:02 PM Martin Sebor via Gcc-patches > wrote: > > > > Hi Ian, > > > > Yesterday's enhancement to -Warray-bounds has exposed a couple of > > issues in libgo where the code writes into an

Re: disable -Warray-bounds in libgo (PR 101374)

2021-07-13 Thread Rainer Orth
Hi Martin, >>> while this patch does fix the libgo bootstrap failure, Go is completely >>> broken: almost 1000 go.test failures and all libgo tests FAIL as well. >>> Seen on both i386-pc-solaris2.11 and sparc-sun-solaris2.11. >> FWIW, I see exactly the same failures on x86_64-pc-linux-gnu, so

Re: disable -Warray-bounds in libgo (PR 101374)

2021-07-12 Thread Martin Sebor via Gcc-patches
On 7/9/21 7:26 AM, Rainer Orth wrote: Hi Martin, Yesterday's enhancement to -Warray-bounds has exposed a couple of issues in libgo where the code writes into an invalid constant address that the warning is designed to flag. On the assumption that those invalid addresses are deliberate, the

Re: disable -Warray-bounds in libgo (PR 101374)

2021-07-09 Thread Ian Lance Taylor via Gcc-patches
On Thu, Jul 8, 2021 at 11:16 PM Richard Biener wrote: > > On Thu, Jul 8, 2021 at 8:02 PM Martin Sebor via Gcc-patches > wrote: > > > > Hi Ian, > > > > Yesterday's enhancement to -Warray-bounds has exposed a couple of > > issues in libgo where the code writes into an invalid constant > > address

Re: disable -Warray-bounds in libgo (PR 101374)

2021-07-09 Thread Martin Sebor via Gcc-patches
On 7/9/21 7:19 AM, Maxim Kuvyrkov wrote: On 9 Jul 2021, at 09:16, Richard Biener via Gcc-patches wrote: On Thu, Jul 8, 2021 at 8:02 PM Martin Sebor via Gcc-patches wrote: Hi Ian, Yesterday's enhancement to -Warray-bounds has exposed a couple of issues in libgo where the code writes into

Re: disable -Warray-bounds in libgo (PR 101374)

2021-07-09 Thread Martin Sebor via Gcc-patches
On 7/9/21 12:16 AM, Richard Biener wrote: On Thu, Jul 8, 2021 at 8:02 PM Martin Sebor via Gcc-patches wrote: Hi Ian, Yesterday's enhancement to -Warray-bounds has exposed a couple of issues in libgo where the code writes into an invalid constant address that the warning is designed to flag.

Re: disable -Warray-bounds in libgo (PR 101374)

2021-07-09 Thread Rainer Orth
Hi Martin, >> Yesterday's enhancement to -Warray-bounds has exposed a couple of >> issues in libgo where the code writes into an invalid constant >> address that the warning is designed to flag. >> >> On the assumption that those invalid addresses are deliberate, >> the attached patch suppresses

Re: disable -Warray-bounds in libgo (PR 101374)

2021-07-09 Thread Maxim Kuvyrkov via Gcc-patches
> On 9 Jul 2021, at 09:16, Richard Biener via Gcc-patches > wrote: > > On Thu, Jul 8, 2021 at 8:02 PM Martin Sebor via Gcc-patches > wrote: >> >> Hi Ian, >> >> Yesterday's enhancement to -Warray-bounds has exposed a couple of >> issues in libgo where the code writes into an invalid constant

Re: disable -Warray-bounds in libgo (PR 101374)

2021-07-09 Thread Richard Biener via Gcc-patches
On Thu, Jul 8, 2021 at 8:02 PM Martin Sebor via Gcc-patches wrote: > > Hi Ian, > > Yesterday's enhancement to -Warray-bounds has exposed a couple of > issues in libgo where the code writes into an invalid constant > address that the warning is designed to flag. > > On the assumption that those

Re: disable -Warray-bounds in libgo (PR 101374)

2021-07-08 Thread Rainer Orth
Hi Martin, > Yesterday's enhancement to -Warray-bounds has exposed a couple of > issues in libgo where the code writes into an invalid constant > address that the warning is designed to flag. > > On the assumption that those invalid addresses are deliberate, > the attached patch suppresses these

disable -Warray-bounds in libgo (PR 101374)

2021-07-08 Thread Martin Sebor via Gcc-patches
Hi Ian, Yesterday's enhancement to -Warray-bounds has exposed a couple of issues in libgo where the code writes into an invalid constant address that the warning is designed to flag. On the assumption that those invalid addresses are deliberate, the attached patch suppresses these instances by