public inbox for gcc-regression@sourceware.org
help / color / mirror / Atom feed
From: "sunil.k.pandey" <skpandey@sc.intel.com>
To: gcc-patches@gcc.gnu.org, gcc-regression@gcc.gnu.org, msebor@redhat.com
Subject: [r12-4725 Regression] FAIL: libgomp.c/doacross-1.c (test for excess errors) on Linux/x86_64
Date: Tue, 26 Oct 2021 22:22:19 -0700	[thread overview]
Message-ID: <20211027052219.DD6AF2864700@gskx-2.sc.intel.com> (raw)

On Linux/x86_64,

88b504b7a8c5affb0ffa97990d22af2b199e36ed is the first bad commit
commit 88b504b7a8c5affb0ffa97990d22af2b199e36ed
Author: Martin Sebor <msebor@redhat.com>
Date:   Tue Oct 26 14:34:16 2021 -0600

    Detect overflow by atomic functions [PR102453].

caused

FAIL: gcc.dg/Warray-bounds-90.c (test for excess errors)
FAIL: gcc.dg/Warray-bounds-90.c  (test for warnings, line 100)
FAIL: gcc.dg/Warray-bounds-90.c  (test for warnings, line 103)
FAIL: gcc.dg/Warray-bounds-90.c  (test for warnings, line 105)
FAIL: gcc.dg/Warray-bounds-90.c  (test for warnings, line 107)
FAIL: gcc.dg/Warray-bounds-90.c  (test for warnings, line 110)
FAIL: gcc.dg/Warray-bounds-90.c  (test for warnings, line 112)
FAIL: gcc.dg/Warray-bounds-90.c  (test for warnings, line 114)
FAIL: gcc.dg/Warray-bounds-90.c  (test for warnings, line 121)
FAIL: gcc.dg/Warray-bounds-90.c  (test for warnings, line 124)
FAIL: gcc.dg/Warray-bounds-90.c  (test for warnings, line 127)
FAIL: gcc.dg/Warray-bounds-90.c  (test for warnings, line 129)
FAIL: gcc.dg/Warray-bounds-90.c  (test for warnings, line 132)
FAIL: gcc.dg/Warray-bounds-90.c  (test for warnings, line 134)
FAIL: gcc.dg/Warray-bounds-90.c  (test for warnings, line 136)
FAIL: gcc.dg/Warray-bounds-90.c  (test for warnings, line 139)
FAIL: gcc.dg/Warray-bounds-90.c  (test for warnings, line 141)
FAIL: gcc.dg/Warray-bounds-90.c  (test for warnings, line 144)
FAIL: gcc.dg/Warray-bounds-90.c  (test for warnings, line 146)
FAIL: gcc.dg/Warray-bounds-90.c  (test for warnings, line 66)
FAIL: gcc.dg/Warray-bounds-90.c  (test for warnings, line 69)
FAIL: gcc.dg/Warray-bounds-90.c  (test for warnings, line 73)
FAIL: gcc.dg/Warray-bounds-90.c  (test for warnings, line 77)
FAIL: gcc.dg/Warray-bounds-90.c  (test for warnings, line 85)
FAIL: gcc.dg/Warray-bounds-90.c  (test for warnings, line 88)
FAIL: gcc.dg/Warray-bounds-90.c  (test for warnings, line 91)
FAIL: gcc.dg/Warray-bounds-90.c  (test for warnings, line 93)
FAIL: gcc.dg/Warray-bounds-90.c  (test for warnings, line 96)
FAIL: gcc.dg/Warray-bounds-90.c  (test for warnings, line 98)
FAIL: libgomp.c/doacross-1.c (test for excess errors)

with GCC configured with

../../gcc/configure --prefix=/local/skpandey/gccwork/toolwork/gcc-bisect-master/master/r12-4725/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/Warray-bounds-90.c --target_board='unix{-m32}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gcc.dg/Warray-bounds-90.c --target_board='unix{-m32\ -march=cascadelake}'"
$ cd {build_dir}/x86_64-linux/libgomp/testsuite && make check RUNTESTFLAGS="c.exp=libgomp.c/doacross-1.c --target_board='unix{-m64}'"
$ cd {build_dir}/x86_64-linux/libgomp/testsuite && make check RUNTESTFLAGS="c.exp=libgomp.c/doacross-1.c --target_board='unix{-m64\ -march=cascadelake}'"

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


             reply	other threads:[~2021-10-27  5:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-27  5:22 sunil.k.pandey [this message]
2021-10-27 13:30 ` Jakub Jelinek
2021-10-27 15:36   ` Martin Sebor
2021-10-27 15:48     ` Tobias Burnus
2021-10-27 16:06       ` 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=20211027052219.DD6AF2864700@gskx-2.sc.intel.com \
    --to=skpandey@sc.intel.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc-regression@gcc.gnu.org \
    --cc=msebor@redhat.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: link
Be 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).