public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/99910] [11/12 Regression] g++.dg/modules/xtreme-header-2_b.C ICE
Date: Wed, 16 Jun 2021 17:27:20 +0000	[thread overview]
Message-ID: <bug-99910-4-18ZPG3G6hJ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99910-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99910

--- Comment #5 from Hans-Peter Nilsson <hp at gcc dot gnu.org> ---
This and several other FAILs have re-appeared on master for cris-elf.
I think my autotester log entry is to the point:

... 2021-06-15-15:17:36 1de31913d20a (f: 88, p: 46598)
*** regress-11 (f: 99, p: 46599), gcc 71790f398e11, cris-elf at
2021-06-15-21:07:02 on pchp3, log at
/x/checkout/gcc_latest/logfile.71790f398e11.2021-06-15-21:07:02
--- regress.prev        2021-06-15 23:04:22.000000000 +0200
+++ regress     2021-06-16 05:26:34.662416022 +0200
@@ -0,0 +1,11 @@
+g++.sum g++.dg/modules/hello-1_b.C
+g++.sum g++.dg/modules/pr99425-2_b.X
+g++.sum g++.dg/modules/string-1_b.C
+g++.sum g++.dg/modules/xtreme-header-1_b.C
+g++.sum g++.dg/modules/xtreme-header-2_b.C
+g++.sum g++.dg/modules/xtreme-header-3_b.C
+g++.sum g++.dg/modules/xtreme-header-4_b.C
+g++.sum g++.dg/modules/xtreme-header-5_b.C
+g++.sum g++.dg/modules/xtreme-header-6_b.C
+g++.sum g++.dg/modules/xtreme-header_b.C
+g++.sum g++.dg/modules/xtreme-tr1_b.C

(No regressions at 1de31913d20a aka. r12-1482
11 regressions as per above at r12-1490)
I haven't looked further into the failures.

  parent reply	other threads:[~2021-06-16 17:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-04 21:51 [Bug c++/99910] New: [11 " hp at gcc dot gnu.org
2021-04-06  8:05 ` [Bug c++/99910] " rguenth at gcc dot gnu.org
2021-04-08  4:13 ` hp at gcc dot gnu.org
2021-04-15  4:11 ` hp at gcc dot gnu.org
2021-04-27 11:40 ` [Bug c++/99910] [11/12 " jakub at gcc dot gnu.org
2021-06-14 12:55 ` clyon at gcc dot gnu.org
2021-06-16 17:27 ` hp at gcc dot gnu.org [this message]
2021-06-16 20:50 ` msebor at gcc dot gnu.org
2021-07-28  7:06 ` rguenth at gcc dot gnu.org
2021-08-09 21:28 ` hp at gcc dot gnu.org
2021-12-30  7:24 ` pinskia at gcc dot gnu.org
2022-04-01  5:41 ` guojiufu 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-99910-4-18ZPG3G6hJ@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).