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-7688 vs commit r12-7683 on Linux/x86_64
Date: Thu, 17 Mar 2022 11:12:05 -0700	[thread overview]
Message-ID: <20220317181205.10B8C65479@gnu-34.sc.intel.com> (raw)

New failures:
FAIL: gcc.target/i386/bt-5.c scan-assembler-not sar[lq][ \t]
FAIL: gcc.target/i386/bt-5.c scan-assembler-times bt[lq][ \t] 7

New passes:
FAIL: gcc.dg/tree-ssa/phi-opt-21.c scan-tree-dump phiopt4 "converted to straightline code"
FAIL: gcc.dg/tree-ssa/phi-opt-21.c scan-tree-dump phiopt4 "converted to straightline code"
FAIL: gcc.dg/tree-ssa/phi-opt-21.c scan-tree-dump phiopt4 "converted to straightline code"
FAIL: gcc.dg/tree-ssa/pr18134.c scan-tree-dump-times optimized "= a_..D. != 0" 1
FAIL: gcc.dg/tree-ssa/pr18134.c scan-tree-dump-times optimized "= a_..D. != 0" 1
FAIL: gcc.dg/tree-ssa/pr18134.c scan-tree-dump-times optimized "= a_..D. != 0" 1
FAIL: gcc.dg/tree-ssa/pr96480.c scan-tree-dump optimized " = _[0-9]* <= 3;"
FAIL: gcc.dg/tree-ssa/pr96480.c scan-tree-dump optimized " = _[0-9]* <= 3;"
FAIL: gcc.dg/tree-ssa/pr96480.c scan-tree-dump optimized " = _[0-9]* <= 3;"
FAIL: gcc.dg/tree-ssa/sccp-2.c scan-tree-dump-times optimized "bb" 1
FAIL: gcc.dg/tree-ssa/sccp-2.c scan-tree-dump-times optimized "bb" 1
FAIL: gcc.dg/tree-ssa/sccp-2.c scan-tree-dump-times optimized "bb" 1
FAIL: gcc.dg/tree-ssa/ssa-hoist-4.c scan-tree-dump-times optimized "MAX_EXPR" 1
FAIL: gcc.dg/tree-ssa/ssa-hoist-4.c scan-tree-dump-times optimized "MAX_EXPR" 1
FAIL: gcc.dg/tree-ssa/ssa-hoist-4.c scan-tree-dump-times optimized "MAX_EXPR" 1
FAIL: gcc.target/i386/pr95852-1.c scan-assembler-times \tjn?o\t 16
FAIL: gcc.target/i386/pr95852-1.c scan-assembler-times \tjn?o\t 16
FAIL: gcc.target/i386/pr95852-1.c scan-assembler-times \tjn?o\t 16
FAIL: gcc.target/i386/pr95852-1.c scan-assembler-times \tsetno\t 8
FAIL: gcc.target/i386/pr95852-1.c scan-assembler-times \tsetno\t 8
FAIL: gcc.target/i386/pr95852-1.c scan-assembler-times \tsetno\t 8
FAIL: gcc.target/i386/pr95852-1.c scan-assembler-times \tseto\t 8
FAIL: gcc.target/i386/pr95852-1.c scan-assembler-times \tseto\t 8
FAIL: gcc.target/i386/pr95852-1.c scan-assembler-times \tseto\t 8
FAIL: gcc.target/i386/pr95852-2.c scan-assembler-times \tjn?o\t 16
FAIL: gcc.target/i386/pr95852-2.c scan-assembler-times \tjn?o\t 16
FAIL: gcc.target/i386/pr95852-2.c scan-assembler-times \tjn?o\t 16
FAIL: gcc.target/i386/pr95852-2.c scan-assembler-times \tseto\t 8
FAIL: gcc.target/i386/pr95852-2.c scan-assembler-times \tseto\t 8
FAIL: gcc.target/i386/pr95852-2.c scan-assembler-times \tseto\t 8
FAIL: gcc.target/i386/pr95852-3.c scan-assembler-times \tjn?o\t 16
FAIL: gcc.target/i386/pr95852-3.c scan-assembler-times \tjn?o\t 16
FAIL: gcc.target/i386/pr95852-3.c scan-assembler-times \tjn?o\t 16
FAIL: gcc.target/i386/pr95852-3.c scan-assembler-times \tsetno\t 8
FAIL: gcc.target/i386/pr95852-3.c scan-assembler-times \tsetno\t 8
FAIL: gcc.target/i386/pr95852-3.c scan-assembler-times \tsetno\t 8
FAIL: gcc.target/i386/pr95852-3.c scan-assembler-times \tseto\t 8
FAIL: gcc.target/i386/pr95852-3.c scan-assembler-times \tseto\t 8
FAIL: gcc.target/i386/pr95852-3.c scan-assembler-times \tseto\t 8
FAIL: gcc.target/i386/pr95852-4.c scan-assembler-times \tjn?o\t 16
FAIL: gcc.target/i386/pr95852-4.c scan-assembler-times \tjn?o\t 16
FAIL: gcc.target/i386/pr95852-4.c scan-assembler-times \tjn?o\t 16
FAIL: gcc.target/i386/pr95852-4.c scan-assembler-times \tseto\t 8
FAIL: gcc.target/i386/pr95852-4.c scan-assembler-times \tseto\t 8
FAIL: gcc.target/i386/pr95852-4.c scan-assembler-times \tseto\t 8


                 reply	other threads:[~2022-03-17 18:16 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=20220317181205.10B8C65479@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).