From: "Jiang, Haochen" <haochen.jiang@intel.com>
To: "vultkayn@gcc.gnu.org" <vultkayn@gcc.gnu.org>,
"gcc-regression@gcc.gnu.org" <gcc-regression@gcc.gnu.org>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
"Jiang, Haochen" <haochen.jiang@intel.com>
Subject: [r14-3823 Regression] FAIL: c-c++-common/analyzer/compound-assignment-1.c -std=c++98 (test for warnings, line 72) on Linux/x86_64
Date: Mon, 11 Sep 2023 08:03:28 +0000 [thread overview]
Message-ID: <SA1PR11MB5946DC03775B3401D3168AC8ECF2A@SA1PR11MB5946.namprd11.prod.outlook.com> (raw)
In-Reply-To: <202309092344.389NiSeQ3407880@shliclel4214.sh.intel.com>
On Linux/x86_64,
50b5199cff690891726877e1c00ac53dfb7cc1c8 is the first bad commit
commit 50b5199cff690891726877e1c00ac53dfb7cc1c8
Author: benjamin priour <vultkayn@gcc.gnu.org>
Date: Sat Sep 9 18:03:56 2023 +0200
analyzer: Move gcc.dg/analyzer tests to c-c++-common (2) [PR96395]
caused
FAIL: c-c++-common/analyzer/compound-assignment-1.c -std=c++14 (test for excess errors)
FAIL: c-c++-common/analyzer/compound-assignment-1.c -std=c++14 (test for warnings, line 72)
FAIL: c-c++-common/analyzer/compound-assignment-1.c -std=c++17 (test for excess errors)
FAIL: c-c++-common/analyzer/compound-assignment-1.c -std=c++17 (test for warnings, line 72)
FAIL: c-c++-common/analyzer/compound-assignment-1.c -std=c++20 (test for excess errors)
FAIL: c-c++-common/analyzer/compound-assignment-1.c -std=c++20 (test for warnings, line 72)
FAIL: c-c++-common/analyzer/compound-assignment-1.c -std=c++98 (test for excess errors)
FAIL: c-c++-common/analyzer/compound-assignment-1.c -std=c++98 (test for warnings, line 72)
with GCC configured with
../../gcc/configure --prefix=/export/users/haochenj/src/gcc-bisect/master/master/r14-3823/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="analyzer.exp=c-c++-common/analyzer/compound-assignment-1.c --target_board='unix{-m32}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="analyzer.exp=c-c++-common/analyzer/compound-assignment-1.c --target_board='unix{-m32\ -march=cascadelake}'"
(If you met problems with cascadelake related, disabling AVX512F in command line might save that.)
(However, please make sure that there is no potential problems with AVX512.)
next parent reply other threads:[~2023-09-11 8:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <202309092344.389NiSeQ3407880@shliclel4214.sh.intel.com>
2023-09-11 8:03 ` Jiang, Haochen [this message]
2023-09-11 17:27 ` Benjamin Priour
2023-09-11 21:11 ` Jakub Jelinek
2023-09-12 7:02 ` [PATCH] testsuite work-around compound-assignment-1.c C++ failures on various targets [PR111377] Jakub Jelinek
2023-09-13 21:58 ` David Malcolm
2023-09-19 7:20 ` Patch ping: " Jakub Jelinek
2023-09-19 14:47 ` David Malcolm
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=SA1PR11MB5946DC03775B3401D3168AC8ECF2A@SA1PR11MB5946.namprd11.prod.outlook.com \
--to=haochen.jiang@intel.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc-regression@gcc.gnu.org \
--cc=vultkayn@gcc.gnu.org \
/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).