public inbox for gcc-regression@sourceware.org
help / color / mirror / Atom feed
From: "H.J. Lu" <hjl@sc.intel.com>
To: skpgkp2@gmail.com, hjl.tools@gmail.com, gcc-regression@gcc.gnu.org
Subject: Regressions on master at commit r12-5143 vs commit r12-5077 on Linux/x86_64
Date: Thu, 11 Nov 2021 02:00:24 -0800 [thread overview]
Message-ID: <20211111100024.A45213C0028@gnu-skl-2.sc.intel.com> (raw)
New failures:
FAIL: 18_support/nested_exception/rethrow_if_nested.cc (test for excess errors)
FAIL: 18_support/nested_exception/rethrow_if_nested.cc (test for excess errors)
FAIL: 18_support/nested_exception/rethrow_if_nested.cc (test for excess errors)
FAIL: 20_util/variant/run.cc (test for excess errors)
FAIL: 20_util/variant/run.cc (test for excess errors)
FAIL: 20_util/variant/run.cc (test for excess errors)
FAIL: gfortran.dg/do_subscript_3.f90 -O (test for excess errors)
FAIL: gfortran.dg/do_subscript_3.f90 -O (test for excess errors)
FAIL: gfortran.dg/do_subscript_3.f90 -O (test for excess errors)
FAIL: gfortran.dg/inline_matmul_17.f90 -O scan-tree-dump-times optimized "matmul_r4" 2
FAIL: gfortran.dg/inline_matmul_17.f90 -O scan-tree-dump-times optimized "matmul_r4" 2
FAIL: gfortran.dg/inline_matmul_17.f90 -O scan-tree-dump-times optimized "matmul_r4" 2
FAIL: std/ranges/adaptors/join.cc (test for excess errors)
New passes:
FAIL: 17_intro/headers/c++1998/49745.cc (test for excess errors)
FAIL: 17_intro/headers/c++1998/49745.cc (test for excess errors)
FAIL: 17_intro/headers/c++1998/49745.cc (test for excess errors)
FAIL: 30_threads/jthread/95989.cc execution test
FAIL: 30_threads/jthread/95989.cc execution test
FAIL: 30_threads/jthread/95989.cc execution test
FAIL: g++.dg/warn/Warray-bounds-16.C -std=gnu++14 scan-tree-dump-not optimized "goto"
FAIL: g++.dg/warn/Warray-bounds-16.C -std=gnu++14 scan-tree-dump-not optimized "goto"
FAIL: g++.dg/warn/Warray-bounds-16.C -std=gnu++14 scan-tree-dump-not optimized "goto"
FAIL: g++.dg/warn/Warray-bounds-16.C -std=gnu++14 (test for excess errors)
FAIL: g++.dg/warn/Warray-bounds-16.C -std=gnu++14 (test for excess errors)
FAIL: g++.dg/warn/Warray-bounds-16.C -std=gnu++14 (test for excess errors)
FAIL: g++.dg/warn/Warray-bounds-16.C -std=gnu++17 scan-tree-dump-not optimized "goto"
FAIL: g++.dg/warn/Warray-bounds-16.C -std=gnu++17 scan-tree-dump-not optimized "goto"
FAIL: g++.dg/warn/Warray-bounds-16.C -std=gnu++17 scan-tree-dump-not optimized "goto"
FAIL: g++.dg/warn/Warray-bounds-16.C -std=gnu++17 (test for excess errors)
FAIL: g++.dg/warn/Warray-bounds-16.C -std=gnu++17 (test for excess errors)
FAIL: g++.dg/warn/Warray-bounds-16.C -std=gnu++17 (test for excess errors)
FAIL: g++.dg/warn/Warray-bounds-16.C -std=gnu++2a scan-tree-dump-not optimized "goto"
FAIL: g++.dg/warn/Warray-bounds-16.C -std=gnu++2a scan-tree-dump-not optimized "goto"
FAIL: g++.dg/warn/Warray-bounds-16.C -std=gnu++2a scan-tree-dump-not optimized "goto"
FAIL: g++.dg/warn/Warray-bounds-16.C -std=gnu++2a (test for excess errors)
FAIL: g++.dg/warn/Warray-bounds-16.C -std=gnu++2a (test for excess errors)
FAIL: g++.dg/warn/Warray-bounds-16.C -std=gnu++2a (test for excess errors)
FAIL: g++.dg/warn/Warray-bounds-16.C -std=gnu++98 scan-tree-dump-not optimized "goto"
FAIL: g++.dg/warn/Warray-bounds-16.C -std=gnu++98 scan-tree-dump-not optimized "goto"
FAIL: g++.dg/warn/Warray-bounds-16.C -std=gnu++98 scan-tree-dump-not optimized "goto"
FAIL: g++.dg/warn/Warray-bounds-16.C -std=gnu++98 (test for excess errors)
FAIL: g++.dg/warn/Warray-bounds-16.C -std=gnu++98 (test for excess errors)
FAIL: g++.dg/warn/Warray-bounds-16.C -std=gnu++98 (test for excess errors)
reply other threads:[~2021-11-11 10:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20211111100024.A45213C0028@gnu-skl-2.sc.intel.com \
--to=hjl@sc.intel.com \
--cc=gcc-regression@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=skpgkp2@gmail.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).