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-3641 vs commit r12-3600 on Linux/x86_64
Date: Sat, 18 Sep 2021 01:47:35 -0700 [thread overview]
Message-ID: <20210918084735.D2F793C001E@gnu-skl-2.sc.intel.com> (raw)
New failures:
FAIL: gcc.target/i386/auto-init-3.c scan-assembler-times fldz 3
FAIL: libgomp.c/../libgomp.c-c++-common/atomic-21.c execution test
New passes:
FAIL: gcc.target/i386/auto-init-2.c scan-rtl-dump-times expand "0xfefefefefefefefe" 3
FAIL: gcc.target/i386/auto-init-2.c scan-rtl-dump-times expand "0xfefefefefefefefe" 3
FAIL: gcc.target/i386/auto-init-2.c scan-rtl-dump-times expand "0xfffffffffefefefe" 2
FAIL: gcc.target/i386/auto-init-2.c scan-rtl-dump-times expand "0xfffffffffefefefe" 2
FAIL: gcc.target/i386/auto-init-4.c scan-rtl-dump-times expand "\\[0xfefefefefefefefe\\]" 1
FAIL: gcc.target/i386/auto-init-4.c scan-rtl-dump-times expand "0xfffffffffefefefe" 1
FAIL: gcc.target/i386/auto-init-4.c scan-rtl-dump-times expand "0xfffffffffffffffe\\]\\) repeated x16" 1
FAIL: gcc.target/i386/auto-init-5.c scan-assembler-times \\.long\t0 14
FAIL: gcc.target/i386/auto-init-padding-3.c scan-assembler movl\t\\$16,
FAIL: gcc.target/i386/auto-init-padding-3.c scan-assembler rep stosq
FAIL: gcc.target/i386/auto-init-padding-7.c scan-assembler-times movq\t\\$0, 2
FAIL: gcc.target/i386/auto-init-padding-8.c scan-assembler-times movq\t\\$0, 2
FAIL: gcc.target/i386/auto-init-padding-9.c scan-assembler rep stosq
FAIL: gfortran.dg/PR100914.f90 -O0 (test for excess errors)
FAIL: gfortran.dg/PR100914.f90 -O0 (test for excess errors)
FAIL: gfortran.dg/PR100914.f90 -O0 (test for excess errors)
FAIL: gfortran.dg/PR100914.f90 -O1 (test for excess errors)
FAIL: gfortran.dg/PR100914.f90 -O1 (test for excess errors)
FAIL: gfortran.dg/PR100914.f90 -O1 (test for excess errors)
FAIL: gfortran.dg/PR100914.f90 -O2 (test for excess errors)
FAIL: gfortran.dg/PR100914.f90 -O2 (test for excess errors)
FAIL: gfortran.dg/PR100914.f90 -O2 (test for excess errors)
FAIL: gfortran.dg/PR100914.f90 -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions (test for excess errors)
FAIL: gfortran.dg/PR100914.f90 -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions (test for excess errors)
FAIL: gfortran.dg/PR100914.f90 -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions (test for excess errors)
FAIL: gfortran.dg/PR100914.f90 -O3 -g (test for excess errors)
FAIL: gfortran.dg/PR100914.f90 -O3 -g (test for excess errors)
FAIL: gfortran.dg/PR100914.f90 -O3 -g (test for excess errors)
FAIL: gfortran.dg/PR100914.f90 -Os (test for excess errors)
FAIL: gfortran.dg/PR100914.f90 -Os (test for excess errors)
FAIL: gfortran.dg/PR100914.f90 -Os (test for excess errors)
reply other threads:[~2021-09-18 8:47 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=20210918084735.D2F793C001E@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).