public inbox for gcc-regression@sourceware.org help / color / mirror / Atom feed
From: Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org> To: msebor@redhat.com Cc: gcc-patches <gcc-patches@gcc.gnu.org>, gcc-regression@gcc.gnu.org, "sunil.k.pandey" <skpandey@sc.intel.com> Subject: 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 Date: Fri, 9 Jul 2021 11:16:32 +0300 [thread overview] Message-ID: <857B7488-B11A-4245-8F31-C60E2ABFCB12@linaro.org> (raw) In-Reply-To: <20210708233529.E81612864701@gskx-2.sc.intel.com> > 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)
next prev parent reply other threads:[~2021-07-09 8:15 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-08 23:35 sunil.k.pandey 2021-07-09 8:16 ` Maxim Kuvyrkov [this message] 2021-07-09 17:42 ` Martin Sebor
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=857B7488-B11A-4245-8F31-C60E2ABFCB12@linaro.org \ --to=maxim.kuvyrkov@linaro.org \ --cc=gcc-patches@gcc.gnu.org \ --cc=gcc-regression@gcc.gnu.org \ --cc=msebor@redhat.com \ --cc=skpandey@sc.intel.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).