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-6655 vs commit r12-6620 on Linux/i686 Date: Tue, 18 Jan 2022 01:15:52 -0800 [thread overview] Message-ID: <20220118091552.D962A1807A0@gnu-snb-1.sc.intel.com> (raw) New failures: FAIL: check-MAINTAINERS.py ERROR: ------------------------------------------- ERROR: couldn't open "/export/gnu/import/git/gcc-test-master-ia32/src-master/gcc/testsuite/../dumpfile.c": no such file or directory ERROR: couldn't open "/export/gnu/import/git/gcc-test-master-ia32/src-master/gcc/testsuite/../dumpfile.c": no such file or directory ERROR: g++.dg/gcov/gcov-17.C : error executing dg-final: can't read "script": no such variable ERROR: g++.dg/gcov/pr98273.C : error executing dg-final: can't read "script": no such variable ERROR: in testcase /export/gnu/import/git/gcc-test-master-ia32/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 info: ERROR: tcl error sourcing /export/gnu/import/git/gcc-test-master-ia32/src-master/gcc/testsuite/gcc.misc-tests/options.exp. New passes: FAIL: g++.dg/torture/pr57993-2.C -O0 (test for excess errors) FAIL: g++.dg/torture/pr57993-2.C -O1 (test for excess errors) FAIL: g++.dg/torture/pr57993-2.C -O2 -flto -fno-use-linker-plugin -flto-partition=none (test for excess errors) FAIL: g++.dg/torture/pr57993-2.C -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects (test for excess errors) FAIL: g++.dg/torture/pr57993-2.C -O2 (test for excess errors) FAIL: g++.dg/torture/pr57993-2.C -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions (test for excess errors) FAIL: g++.dg/torture/pr57993-2.C -O3 -g (test for excess errors) FAIL: g++.dg/torture/pr57993-2.C -Os (test for excess errors) FAIL: gfortran.dg/gomp/allocate-2.f90 -O (test for errors, line 36) FAIL: gfortran.dg/ieee/signaling_3.f90 -O0 execution test FAIL: gfortran.dg/ieee/signaling_3.f90 -O1 execution test FAIL: gfortran.dg/ieee/signaling_3.f90 -O2 execution test FAIL: gfortran.dg/ieee/signaling_3.f90 -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions execution test FAIL: gfortran.dg/ieee/signaling_3.f90 -O3 -g execution test FAIL: gfortran.dg/ieee/signaling_3.f90 -Os execution test FAIL: maintainers-verify.sh
reply other threads:[~2022-01-18 9:15 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=20220118091552.D962A1807A0@gnu-snb-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).