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 r13-2162 vs commit r13-2159 on Linux/x86_64
Date: Tue, 23 Aug 2022 21:17:45 -0700	[thread overview]
Message-ID: <20220824041745.9A56162151@gnu-34.sc.intel.com> (raw)

New failures:

New passes:
FAIL: gcc.target/x86_64/abi/bf16/test_basic_returning.c execution,  -O0 
FAIL: gcc.target/x86_64/abi/bf16/test_basic_returning.c execution,  -O1 
FAIL: gcc.target/x86_64/abi/bf16/test_basic_returning.c execution,  -O2 
FAIL: gcc.target/x86_64/abi/bf16/test_basic_returning.c execution,  -O3 -g 
FAIL: gcc.target/x86_64/abi/bf16/test_basic_returning.c execution,  -Og -g 
FAIL: gcc.target/x86_64/abi/bf16/test_basic_returning.c execution,  -Os 
FAIL: gcc.target/x86_64/abi/bf16/test_m128_returning.c execution,  -O0 
FAIL: gcc.target/x86_64/abi/bf16/test_m128_returning.c execution,  -O1 
FAIL: gcc.target/x86_64/abi/bf16/test_m128_returning.c execution,  -O2 
FAIL: gcc.target/x86_64/abi/bf16/test_m128_returning.c execution,  -O3 -g 
FAIL: gcc.target/x86_64/abi/bf16/test_m128_returning.c execution,  -Og -g 
FAIL: gcc.target/x86_64/abi/bf16/test_m128_returning.c execution,  -Os 
FAIL: gcc.target/x86_64/abi/bf16/test_passing_floats.c execution,  -O0 
FAIL: gcc.target/x86_64/abi/bf16/test_passing_floats.c execution,  -O1 
FAIL: gcc.target/x86_64/abi/bf16/test_passing_floats.c execution,  -O2 
FAIL: gcc.target/x86_64/abi/bf16/test_passing_floats.c execution,  -O3 -g 
FAIL: gcc.target/x86_64/abi/bf16/test_passing_floats.c execution,  -Og -g 
FAIL: gcc.target/x86_64/abi/bf16/test_passing_floats.c execution,  -Os 
FAIL: gcc.target/x86_64/abi/bf16/test_passing_m128.c execution,  -O0 
FAIL: gcc.target/x86_64/abi/bf16/test_passing_m128.c execution,  -O1 
FAIL: gcc.target/x86_64/abi/bf16/test_passing_m128.c execution,  -O2 
FAIL: gcc.target/x86_64/abi/bf16/test_passing_m128.c execution,  -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions 
FAIL: gcc.target/x86_64/abi/bf16/test_passing_m128.c execution,  -O3 -g 
FAIL: gcc.target/x86_64/abi/bf16/test_passing_m128.c execution,  -Og -g 
FAIL: gcc.target/x86_64/abi/bf16/test_passing_m128.c execution,  -Os 
FAIL: gcc.target/x86_64/abi/bf16/test_passing_structs.c execution,  -O0 
FAIL: gcc.target/x86_64/abi/bf16/test_passing_structs.c execution,  -O1 
FAIL: gcc.target/x86_64/abi/bf16/test_passing_structs.c execution,  -O2 
FAIL: gcc.target/x86_64/abi/bf16/test_passing_structs.c execution,  -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions 
FAIL: gcc.target/x86_64/abi/bf16/test_passing_structs.c execution,  -O3 -g 
FAIL: gcc.target/x86_64/abi/bf16/test_passing_structs.c execution,  -Og -g 
FAIL: gcc.target/x86_64/abi/bf16/test_passing_structs.c execution,  -Os 
FAIL: gcc.target/x86_64/abi/bf16/test_passing_unions.c execution,  -O0 
FAIL: gcc.target/x86_64/abi/bf16/test_passing_unions.c execution,  -O1 
FAIL: gcc.target/x86_64/abi/bf16/test_passing_unions.c execution,  -O2 
FAIL: gcc.target/x86_64/abi/bf16/test_passing_unions.c execution,  -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions 
FAIL: gcc.target/x86_64/abi/bf16/test_passing_unions.c execution,  -O3 -g 
FAIL: gcc.target/x86_64/abi/bf16/test_passing_unions.c execution,  -Og -g 
FAIL: gcc.target/x86_64/abi/bf16/test_passing_unions.c execution,  -Os 
FAIL: gcc.target/x86_64/abi/bf16/test_struct_returning.c execution,  -O0 
FAIL: gcc.target/x86_64/abi/bf16/test_struct_returning.c execution,  -O1 
FAIL: gcc.target/x86_64/abi/bf16/test_struct_returning.c execution,  -O2 
FAIL: gcc.target/x86_64/abi/bf16/test_struct_returning.c execution,  -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions 
FAIL: gcc.target/x86_64/abi/bf16/test_struct_returning.c execution,  -O3 -g 
FAIL: gcc.target/x86_64/abi/bf16/test_struct_returning.c execution,  -Og -g 
FAIL: gcc.target/x86_64/abi/bf16/test_struct_returning.c execution,  -Os 
FAIL: gcc.target/x86_64/abi/bf16/test_varargs-m128.c execution,  -O0 
FAIL: gcc.target/x86_64/abi/bf16/test_varargs-m128.c execution,  -O1 
FAIL: gcc.target/x86_64/abi/bf16/test_varargs-m128.c execution,  -O2 
FAIL: gcc.target/x86_64/abi/bf16/test_varargs-m128.c execution,  -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions 
FAIL: gcc.target/x86_64/abi/bf16/test_varargs-m128.c execution,  -O3 -g 
FAIL: gcc.target/x86_64/abi/bf16/test_varargs-m128.c execution,  -Og -g 
FAIL: gcc.target/x86_64/abi/bf16/test_varargs-m128.c execution,  -Os 

                 reply	other threads:[~2022-08-24  4:17 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=20220824041745.9A56162151@gnu-34.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).