public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/98926] [11 regression] several ICEs after r11-7011
Date: Wed, 03 Feb 2021 00:08:28 +0000 [thread overview]
Message-ID: <bug-98926-4-qhLECqAsfO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98926-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98926
--- Comment #8 from seurer at gcc dot gnu.org ---
Here was what I saw on a power 8 comparing r11-7010 with r11-7011:
previous run: g:bec5dbae5649da4bd7ea2731a8446ac481cb78ab, r11-7010: 50 failures
this run : g:6e0a231a4aa2407bb7167daf98a37795a67364d8, r11-7011: 61 failures
FAIL: g++.dg/cpp0x/alias-decl-52.C -std=c++2a (internal compiler error)
FAIL: g++.dg/cpp0x/alias-decl-52.C -std=c++2a (test for excess errors)
FAIL: g++.dg/lto/pr65549 cp_lto_pr65549_0.o assemble, -std=gnu++14 -flto -g
-O2 -fno-inline -flto-partition=max -Wno-return-type (internal compiler error)
FAIL: g++.dg/lto/pr65549 cp_lto_pr65549_0.o assemble, -std=gnu++14 -flto -g
-Wno-return-type (internal compiler error)
FAIL: g++.dg/pr77550.C (test for excess errors)
FAIL: g++.dg/warn/Warray-bounds15.C -std=gnu++14 (test for warnings, line 38)
FAIL: g++.dg/warn/Warray-bounds15.C -std=gnu++14 (internal compiler error)
FAIL: g++.dg/warn/Warray-bounds15.C -std=gnu++14 (test for excess errors)
FAIL: g++.dg/warn/Warray-bounds15.C -std=gnu++17 (test for warnings, line 38)
FAIL: g++.dg/warn/Warray-bounds15.C -std=gnu++17 (internal compiler error)
FAIL: g++.dg/warn/Warray-bounds15.C -std=gnu++17 (test for excess errors)
next prev parent reply other threads:[~2021-02-03 0:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 23:50 [Bug other/98926] New: " seurer at gcc dot gnu.org
2021-02-01 23:56 ` [Bug other/98926] " jakub at gcc dot gnu.org
2021-02-02 2:42 ` dje at gcc dot gnu.org
2021-02-02 8:51 ` [Bug c++/98926] " jakub at gcc dot gnu.org
2021-02-02 13:58 ` seurer at gcc dot gnu.org
2021-02-02 15:51 ` seurer at gcc dot gnu.org
2021-02-02 17:15 ` jason at gcc dot gnu.org
2021-02-02 22:48 ` jason at gcc dot gnu.org
2021-02-02 22:55 ` jakub at gcc dot gnu.org
2021-02-02 23:43 ` seurer at gcc dot gnu.org
2021-02-03 0:08 ` seurer at gcc dot gnu.org [this message]
2021-02-03 17:51 ` cvs-commit at gcc dot gnu.org
2021-02-03 22:38 ` seurer at gcc dot gnu.org
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=bug-98926-4-qhLECqAsfO@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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).