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 other/100759] [12 regression] ICE for g++.dg/torture/pr81360.C after r12-1039 at gcc/options-save.c:13626 Date: Wed, 26 May 2021 03:35:26 +0000 [thread overview] Message-ID: <bug-100759-4-iFbVfoMJDH@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100759-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100759 --- Comment #1 from seurer at gcc dot gnu.org --- actually, there are a bunch of failures from this revision: FAIL: g++.dg/torture/pr81360.C -Os (internal compiler error) FAIL: g++.dg/torture/pr81360.C -Os (internal compiler error) FAIL: g++.dg/torture/pr81360.C -Os (test for excess errors) FAIL: g++.dg/torture/pr81360.C -Os (test for excess errors) FAIL: gcc.dg/Warray-bounds-57.c (internal compiler error) FAIL: gcc.dg/Warray-bounds-57.c (internal compiler error) FAIL: gcc.dg/Warray-bounds-57.c (test for excess errors) FAIL: gcc.dg/Warray-bounds-57.c (test for excess errors) FAIL: gcc.dg/pr92860-2.c (test for warnings, line 12) FAIL: gcc.dg/pr92860-2.c (test for warnings, line 12) FAIL: gcc.dg/pr92860-2.c (test for warnings, line 9) FAIL: gcc.dg/pr92860-2.c (test for warnings, line 9) FAIL: gcc.dg/pr92860-2.c (internal compiler error) FAIL: gcc.dg/pr92860-2.c (internal compiler error) FAIL: gcc.dg/pr92860-2.c (test for excess errors) FAIL: gcc.dg/pr92860-2.c (test for excess errors)
next prev parent reply other threads:[~2021-05-26 3:35 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-25 23:26 [Bug other/100759] New: " seurer at gcc dot gnu.org 2021-05-26 3:35 ` seurer at gcc dot gnu.org [this message] 2021-05-26 7:11 ` [Bug other/100759] " marxin at gcc dot gnu.org 2021-05-26 7:52 ` rguenth at gcc dot gnu.org 2021-06-01 13:24 ` cvs-commit at gcc dot gnu.org 2021-06-01 13:24 ` marxin 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-100759-4-iFbVfoMJDH@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: linkBe 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).