[r12-2132 Regression] FAIL: g++.dg/warn/Warray-bounds-20.C -std=gnu++98 note (test for warnings, line 55) on Linux/x86_64

[r12-2132 Regression] FAIL: g++.dg/warn/Warray-bounds-20.C -std=gnu++98 note (test for warnings, line 55) on Linux/x86_64

[sunil.k.pandey]

On Linux/x86_64,

a110855667782dac7b674d3e328b253b3b3c919b is the first bad commit
commit a110855667782dac7b674d3e328b253b3b3c919b
Author: Martin Sebor <msebor@redhat.com>
Date:   Wed Jul 7 14:05:25 2021 -0600

    Correct handling of variable offset minus constant in -Warray-bounds [PR100137]

caused

FAIL: gcc.dg/Wstringop-overflow-47.c pr97027 (test for warnings, line 34)
FAIL: gcc.dg/Wstringop-overflow-47.c pr97027 (test for warnings, line 37)
FAIL: gcc.dg/Wstringop-overflow-47.c pr97027 (test for warnings, line 42)
FAIL: g++.dg/warn/Warray-bounds-20.C  -std=gnu++14 note (test for warnings, line 38)
FAIL: g++.dg/warn/Warray-bounds-20.C  -std=gnu++14 note (test for warnings, line 55)
FAIL: g++.dg/warn/Warray-bounds-20.C  -std=gnu++17 note (test for warnings, line 38)
FAIL: g++.dg/warn/Warray-bounds-20.C  -std=gnu++17 note (test for warnings, line 55)
FAIL: g++.dg/warn/Warray-bounds-20.C  -std=gnu++2a note (test for warnings, line 38)
FAIL: g++.dg/warn/Warray-bounds-20.C  -std=gnu++2a note (test for warnings, line 55)
FAIL: g++.dg/warn/Warray-bounds-20.C  -std=gnu++98 note (test for warnings, line 38)
FAIL: g++.dg/warn/Warray-bounds-20.C  -std=gnu++98 note (test for warnings, line 55)

with GCC configured with

../../gcc/configure --prefix=/local/skpandey/gccwork/toolwork/gcc-bisect-master/master/r12-2132/usr --enable-clocale=gnu --with-system-zlib --with-demangler-in-ld --with-fpmath=sse --enable-languages=c,c++,fortran --enable-cet --without-isl --enable-libmpx x86_64-linux --disable-bootstrap

To reproduce:

$ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gcc.dg/Wstringop-overflow-47.c --target_board='unix{-m32\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gcc.dg/Wstringop-overflow-47.c --target_board='unix{-m64\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=g++.dg/warn/Warray-bounds-20.C --target_board='unix{-m32}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=g++.dg/warn/Warray-bounds-20.C --target_board='unix{-m32\ -march=cascadelake}'"

(Please do not reply to this email, for question about this report, contact me at skpgkp2 at gmail dot com)

Re: [r12-2132 Regression] FAIL: g++.dg/warn/Warray-bounds-20.C -std=gnu++98 note (test for warnings, line 55) on Linux/x86_64

[Maxim Kuvyrkov]

> On 9 Jul 2021, at 02:35, sunil.k.pandey via Gcc-patches <gcc-patches@gcc.gnu.org> wrote:
> 
> On Linux/x86_64,
> 
> a110855667782dac7b674d3e328b253b3b3c919b is the first bad commit
> commit a110855667782dac7b674d3e328b253b3b3c919b
> Author: Martin Sebor <msebor@redhat.com>
> Date:   Wed Jul 7 14:05:25 2021 -0600
> 
>    Correct handling of variable offset minus constant in -Warray-bounds [PR100137]
> 
> caused

Hi Martin,

I see these failing on aarch64-linux-gnu as well:

> 
> FAIL: gcc.dg/Wstringop-overflow-47.c pr97027 (test for warnings, line 34)
> FAIL: gcc.dg/Wstringop-overflow-47.c pr97027 (test for warnings, line 37)
> FAIL: gcc.dg/Wstringop-overflow-47.c pr97027 (test for warnings, line 42)


FWIW, I don’t see these on aarch64-linux-gnu:

> FAIL: g++.dg/warn/Warray-bounds-20.C  -std=gnu++14 note (test for warnings, line 38)
> FAIL: g++.dg/warn/Warray-bounds-20.C  -std=gnu++14 note (test for warnings, line 55)
> FAIL: g++.dg/warn/Warray-bounds-20.C  -std=gnu++17 note (test for warnings, line 38)
> FAIL: g++.dg/warn/Warray-bounds-20.C  -std=gnu++17 note (test for warnings, line 55)
> FAIL: g++.dg/warn/Warray-bounds-20.C  -std=gnu++2a note (test for warnings, line 38)
> FAIL: g++.dg/warn/Warray-bounds-20.C  -std=gnu++2a note (test for warnings, line 55)
> FAIL: g++.dg/warn/Warray-bounds-20.C  -std=gnu++98 note (test for warnings, line 38)
> FAIL: g++.dg/warn/Warray-bounds-20.C  -std=gnu++98 note (test for warnings, line 55)


--
Maxim Kuvyrkov
https://www.linaro.org


> 
> with GCC configured with
> 
> ../../gcc/configure --prefix=/local/skpandey/gccwork/toolwork/gcc-bisect-master/master/r12-2132/usr --enable-clocale=gnu --with-system-zlib --with-demangler-in-ld --with-fpmath=sse --enable-languages=c,c++,fortran --enable-cet --without-isl --enable-libmpx x86_64-linux --disable-bootstrap
> 
> To reproduce:
> 
> $ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gcc.dg/Wstringop-overflow-47.c --target_board='unix{-m32\ -march=cascadelake}'"
> $ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gcc.dg/Wstringop-overflow-47.c --target_board='unix{-m64\ -march=cascadelake}'"
> $ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=g++.dg/warn/Warray-bounds-20.C --target_board='unix{-m32}'"
> $ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=g++.dg/warn/Warray-bounds-20.C --target_board='unix{-m32\ -march=cascadelake}'"
> 
> (Please do not reply to this email, for question about this report, contact me at skpgkp2 at gmail dot com)

Re: [r12-2132 Regression] FAIL: g++.dg/warn/Warray-bounds-20.C -std=gnu++98 note (test for warnings, line 55) on Linux/x86_64

[Martin Sebor]

On 7/9/21 2:16 AM, Maxim Kuvyrkov via Gcc-patches wrote:
>> On 9 Jul 2021, at 02:35, sunil.k.pandey via Gcc-patches <gcc-patches@gcc.gnu.org> wrote:
>>
>> On Linux/x86_64,
>>
>> a110855667782dac7b674d3e328b253b3b3c919b is the first bad commit
>> commit a110855667782dac7b674d3e328b253b3b3c919b
>> Author: Martin Sebor <msebor@redhat.com>
>> Date:   Wed Jul 7 14:05:25 2021 -0600
>>
>>     Correct handling of variable offset minus constant in -Warray-bounds [PR100137]
>>
>> caused
> 
> Hi Martin,
> 
> I see these failing on aarch64-linux-gnu as well:
> 
>>
>> FAIL: gcc.dg/Wstringop-overflow-47.c pr97027 (test for warnings, line 34)
>> FAIL: gcc.dg/Wstringop-overflow-47.c pr97027 (test for warnings, line 37)
>> FAIL: gcc.dg/Wstringop-overflow-47.c pr97027 (test for warnings, line 42)

Thanks.  It looks like I removed the xfails a little bit too
indiscriminately.  The test passes with an x84_64 compiler but
the aarch64 IL still isn't handled.  Let me take care of that.

> 
> 
> FWIW, I don’t see these on aarch64-linux-gnu:

Good! :)  I fixed these problems just yesterday.

Martin

> 
>> FAIL: g++.dg/warn/Warray-bounds-20.C  -std=gnu++14 note (test for warnings, line 38)
>> FAIL: g++.dg/warn/Warray-bounds-20.C  -std=gnu++14 note (test for warnings, line 55)
>> FAIL: g++.dg/warn/Warray-bounds-20.C  -std=gnu++17 note (test for warnings, line 38)
>> FAIL: g++.dg/warn/Warray-bounds-20.C  -std=gnu++17 note (test for warnings, line 55)
>> FAIL: g++.dg/warn/Warray-bounds-20.C  -std=gnu++2a note (test for warnings, line 38)
>> FAIL: g++.dg/warn/Warray-bounds-20.C  -std=gnu++2a note (test for warnings, line 55)
>> FAIL: g++.dg/warn/Warray-bounds-20.C  -std=gnu++98 note (test for warnings, line 38)
>> FAIL: g++.dg/warn/Warray-bounds-20.C  -std=gnu++98 note (test for warnings, line 55)
> 
> 
> --
> Maxim Kuvyrkov
> https://www.linaro.org
> 
> 
>>
>> with GCC configured with
>>
>> ../../gcc/configure --prefix=/local/skpandey/gccwork/toolwork/gcc-bisect-master/master/r12-2132/usr --enable-clocale=gnu --with-system-zlib --with-demangler-in-ld --with-fpmath=sse --enable-languages=c,c++,fortran --enable-cet --without-isl --enable-libmpx x86_64-linux --disable-bootstrap
>>
>> To reproduce:
>>
>> $ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gcc.dg/Wstringop-overflow-47.c --target_board='unix{-m32\ -march=cascadelake}'"
>> $ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gcc.dg/Wstringop-overflow-47.c --target_board='unix{-m64\ -march=cascadelake}'"
>> $ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=g++.dg/warn/Warray-bounds-20.C --target_board='unix{-m32}'"
>> $ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=g++.dg/warn/Warray-bounds-20.C --target_board='unix{-m32\ -march=cascadelake}'"
>>
>> (Please do not reply to this email, for question about this report, contact me at skpgkp2 at gmail dot com)
>