public inbox for gcc-regression@sourceware.org
help / color / mirror / Atom feed
From: "H. J. Lu" <hjl@sc.intel.com>
To: haochen.jiang@intel.com, hjl.tools@gmail.com, gcc-regression@gcc.gnu.org
Subject: Regressions on native/master at commit r13-3359 vs commit r13-3350 on Linux/x86_64
Date: Tue, 18 Oct 2022 08:58:20 -0700	[thread overview]
Message-ID: <20221018155820.71D063E001E@gnu-clx-1.sc.intel.com> (raw)

Regressions on native/master at commit r13-3359 vs commit r13-3350 on Linux/x86_64
New failures:
FAIL: libgomp.c++/loop-13.C execution test
FAIL: libgomp.c++/loop-13.C execution test
FAIL: libgomp.c++/loop-13.C (internal compiler error: verify_ssa failed)
FAIL: libgomp.c++/loop-14.C execution test
FAIL: libgomp.c++/loop-14.C execution test
FAIL: libgomp.c++/loop-14.C (internal compiler error: verify_ssa failed)

New passes:
FAIL: gcc.dg/tree-ssa/forwprop-19.c scan-tree-dump-not forwprop1 "VEC_PERM_EXPR"
FAIL: gcc.dg/tree-ssa/forwprop-19.c scan-tree-dump-not forwprop1 "VEC_PERM_EXPR"
FAIL: gcc.dg/tree-ssa/forwprop-19.c scan-tree-dump-not forwprop1 "VEC_PERM_EXPR"
FAIL: libgomp.c++/loop-13.C (internal compiler error: in as_a, at is-a.h:242)
FAIL: libgomp.c++/loop-13.C (internal compiler error: in as_a, at is-a.h:242)
FAIL: libgomp.c++/loop-13.C (internal compiler error: in as_a, at is-a.h:242)
FAIL: libgomp.c++/loop-13.C (test for excess errors)
FAIL: libgomp.c++/loop-13.C (test for excess errors)
FAIL: libgomp.c++/loop-14.C (internal compiler error: in as_a, at is-a.h:242)
FAIL: libgomp.c++/loop-14.C (internal compiler error: in as_a, at is-a.h:242)
FAIL: libgomp.c++/loop-14.C (internal compiler error: in as_a, at is-a.h:242)
FAIL: libgomp.c++/loop-14.C (test for excess errors)
FAIL: libgomp.c++/loop-14.C (test for excess errors)

                 reply	other threads:[~2022-10-18 15:58 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=20221018155820.71D063E001E@gnu-clx-1.sc.intel.com \
    --to=hjl@sc.intel.com \
    --cc=gcc-regression@gcc.gnu.org \
    --cc=haochen.jiang@intel.com \
    --cc=hjl.tools@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).