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-1971 vs commit r13-1954 on Linux/i686
Date: Fri, 05 Aug 2022 00:32:34 -0700	[thread overview]
Message-ID: <20220805073234.92FF8400BCA@gnu-hsw-1.sc.intel.com> (raw)

New failures:
FAIL: gfortran.dg/class_optional_2.f90   -O1  (internal compiler error: verify_ssa failed)
FAIL: gfortran.dg/class_optional_2.f90   -O1  (test for excess errors)
FAIL: libstdc++-prettyprinters/48362.cc print t2
FAIL: libstdc++-prettyprinters/48362.cc print t2
FAIL: libstdc++-prettyprinters/cxx11.cc print rtpl
FAIL: libstdc++-prettyprinters/cxx11.cc print rtpl
FAIL: libstdc++-prettyprinters/cxx11.cc print tpl
FAIL: libstdc++-prettyprinters/cxx11.cc print tpl

New passes:
FAIL: gcc.dg/analyzer/pr96653.c (internal compiler error: in gimple_phi_arg, at gimple.h:4594)
FAIL: gcc.dg/analyzer/pr96653.c (test for excess errors)
FAIL: g++.dg/warn/uninit-pr105562.C  -std=gnu++14 (internal compiler error: in gimple_phi_arg, at gimple.h:4594)
FAIL: g++.dg/warn/uninit-pr105562.C  -std=gnu++14 (test for excess errors)
FAIL: g++.dg/warn/uninit-pr105562.C  -std=gnu++17 (internal compiler error: in gimple_phi_arg, at gimple.h:4594)
FAIL: g++.dg/warn/uninit-pr105562.C  -std=gnu++17 (test for excess errors)
FAIL: g++.dg/warn/uninit-pr105562.C  -std=gnu++20 (internal compiler error: in gimple_phi_arg, at gimple.h:4594)
FAIL: g++.dg/warn/uninit-pr105562.C  -std=gnu++20 (test for excess errors)
FAIL: gfortran.dg/make_unit.f90   -O1  (internal compiler error: in gimple_phi_arg, at gimple.h:4594)
FAIL: gfortran.dg/make_unit.f90   -O1  (test for excess errors)


                 reply	other threads:[~2022-08-05  7:32 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=20220805073234.92FF8400BCA@gnu-hsw-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: 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).