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 native/master at commit r12-6675 vs commit r12-6653 on Linux/x86_64 Date: Tue, 18 Jan 2022 08:57:30 -0800 [thread overview] Message-ID: <20220118165730.115C23E001F@gnu-clx-1.sc.intel.com> (raw) New failures: FAIL: gcc.target/i386/avx512er-vrcp28ps-4.c scan-assembler-times vrcp28ps[^\n\r]*zmm[0-9]+(?:\n|[ \\t]+#) 1 New passes: FAIL: check-MAINTAINERS.py FAIL: check-MAINTAINERS.py FAIL: check-MAINTAINERS.py FAIL: gcc.target/i386/avx512er-vrsqrt28ps-4.c scan-assembler-times vrsqrt28ps[^\n\r]*zmm[0-9]+(?:\n|[ \\t]+#) 1 FAIL: gcc.target/i386/avx512fp16-v4hf-concat.c scan-assembler-times vpunpcklqdq 1 FAIL: gcc.target/i386/minmax-9.c scan-assembler-times test 3 FAIL: gcc.target/i386/pr103973-11.c scan-assembler-times \tcomiss 4 FAIL: gcc.target/i386/pr103973-11.c scan-assembler-times \tcomiss 4 FAIL: gcc.target/i386/pr103973-13.c scan-assembler-times \tcomisd 4 FAIL: gcc.target/i386/pr103973-13.c scan-assembler-times \tcomisd 4 FAIL: gcc.target/i386/pr103973-15.c scan-assembler-times \tcomiss 4 FAIL: gcc.target/i386/pr103973-15.c scan-assembler-times \tcomiss 4 FAIL: gcc.target/i386/pr103973-1.c scan-assembler-times \tcomisd 4 FAIL: gcc.target/i386/pr103973-1.c scan-assembler-times \tcomisd 4 FAIL: gcc.target/i386/pr103973-3.c scan-assembler-times \tcomiss 4 FAIL: gcc.target/i386/pr103973-3.c scan-assembler-times \tcomiss 4 FAIL: gcc.target/i386/pr103973-5.c scan-assembler-times \tcomisd 4 FAIL: gcc.target/i386/pr103973-5.c scan-assembler-times \tcomisd 4 FAIL: gcc.target/i386/pr103973-7.c scan-assembler-times \tcomiss 4 FAIL: gcc.target/i386/pr103973-7.c scan-assembler-times \tcomiss 4 FAIL: gcc.target/i386/pr103973-9.c scan-assembler-times \tcomisd 4 FAIL: gcc.target/i386/pr103973-9.c scan-assembler-times \tcomisd 4 FAIL: g++.target/i386/pr103973-11.C scan-assembler-times \tcomiss 2 FAIL: g++.target/i386/pr103973-11.C scan-assembler-times \tcomiss 2 FAIL: g++.target/i386/pr103973-13.C scan-assembler-times \tcomisd 2 FAIL: g++.target/i386/pr103973-13.C scan-assembler-times \tcomisd 2 FAIL: g++.target/i386/pr103973-15.C scan-assembler-times \tcomiss 2 FAIL: g++.target/i386/pr103973-15.C scan-assembler-times \tcomiss 2 FAIL: g++.target/i386/pr103973-1.C scan-assembler-times \tcomisd 2 FAIL: g++.target/i386/pr103973-1.C scan-assembler-times \tcomisd 2 FAIL: g++.target/i386/pr103973-3.C scan-assembler-times \tcomiss 2 FAIL: g++.target/i386/pr103973-3.C scan-assembler-times \tcomiss 2 FAIL: g++.target/i386/pr103973-5.C scan-assembler-times \tcomisd 2 FAIL: g++.target/i386/pr103973-5.C scan-assembler-times \tcomisd 2 FAIL: g++.target/i386/pr103973-7.C scan-assembler-times \tcomiss 2 FAIL: g++.target/i386/pr103973-7.C scan-assembler-times \tcomiss 2 FAIL: g++.target/i386/pr103973-9.C scan-assembler-times \tcomisd 2 FAIL: g++.target/i386/pr103973-9.C scan-assembler-times \tcomisd 2 ERROR: ------------------------------------------- ERROR: ------------------------------------------- ERROR: ------------------------------------------- ERROR: couldn't open "/export/gnu/import/git/gcc-test-master-intel64-native/src-master/gcc/testsuite/../dumpfile.c": no such file or directory ERROR: couldn't open "/export/gnu/import/git/gcc-test-master-intel64-native/src-master/gcc/testsuite/../dumpfile.c": no such file or directory ERROR: couldn't open "/export/gnu/import/git/gcc-test-master-intel64-native/src-master/gcc/testsuite/../dumpfile.c": no such file or directory ERROR: couldn't open "/export/gnu/import/git/gcc-test-master-intel64-native/src-master/gcc/testsuite/../dumpfile.c": no such file or directory ERROR: couldn't open "/export/gnu/import/git/gcc-test-master-intel64-native/src-master/gcc/testsuite/../dumpfile.c": no such file or directory ERROR: couldn't open "/export/gnu/import/git/gcc-test-master-intel64-native/src-master/gcc/testsuite/../dumpfile.c": no such file or directory ERROR: in testcase /export/gnu/import/git/gcc-test-master-intel64-native/src-master/gcc/testsuite/gcc.misc-tests/options.exp ERROR: in testcase /export/gnu/import/git/gcc-test-master-intel64-native/src-master/gcc/testsuite/gcc.misc-tests/options.exp ERROR: in testcase /export/gnu/import/git/gcc-test-master-intel64-native/src-master/gcc/testsuite/gcc.misc-tests/options.exp ERROR: tcl error code POSIX ENOENT {no such file or directory} ERROR: tcl error code POSIX ENOENT {no such file or directory} ERROR: tcl error code POSIX ENOENT {no such file or directory} ERROR: tcl error code POSIX ENOENT {no such file or directory} ERROR: tcl error code POSIX ENOENT {no such file or directory} ERROR: tcl error code POSIX ENOENT {no such file or directory} ERROR: tcl error info: ERROR: tcl error info: ERROR: tcl error info: ERROR: tcl error sourcing /export/gnu/import/git/gcc-test-master-intel64-native/src-master/gcc/testsuite/gcc.misc-tests/options.exp. ERROR: tcl error sourcing /export/gnu/import/git/gcc-test-master-intel64-native/src-master/gcc/testsuite/gcc.misc-tests/options.exp. ERROR: tcl error sourcing /export/gnu/import/git/gcc-test-master-intel64-native/src-master/gcc/testsuite/gcc.misc-tests/options.exp.
reply other threads:[~2022-01-18 16:57 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=20220118165730.115C23E001F@gnu-clx-1.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: 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).