public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/105297] New: [12 Regression] new modules 'xtreme' test cases FAILs Date: Sat, 16 Apr 2022 20:21:12 +0000 [thread overview] Message-ID: <bug-105297-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105297 Bug ID: 105297 Summary: [12 Regression] new modules 'xtreme' test cases FAILs Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: iains at gcc dot gnu.org Target Milestone: --- between r12-8146 and r12-8179. for each std= tested g++.dg/modules/xtreme-header-4_a.H -std=c++* (internal compiler error: in insert, at cp/module.cc:4800) likewise g++.dg/modules/xtreme-header_a.H
next reply other threads:[~2022-04-16 20:21 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-16 20:21 iains at gcc dot gnu.org [this message] 2022-04-16 20:22 ` [Bug c++/105297] " iains at gcc dot gnu.org 2022-04-20 13:53 ` jakub at gcc dot gnu.org 2022-04-20 13:59 ` jakub at gcc dot gnu.org 2022-04-20 14:23 ` jakub at gcc dot gnu.org 2022-04-20 14:29 ` jakub at gcc dot gnu.org 2022-04-20 14:31 ` hp at gcc dot gnu.org 2022-04-20 16:01 ` redi at gcc dot gnu.org 2022-04-20 16:14 ` ppalka at gcc dot gnu.org 2022-04-20 16:18 ` ppalka at gcc dot gnu.org 2022-04-20 17:17 ` jakub at gcc dot gnu.org 2022-04-20 17:59 ` ppalka at gcc dot gnu.org 2022-04-21 9:25 ` guojiufu at gcc dot gnu.org 2022-04-21 12:35 ` cvs-commit at gcc dot gnu.org 2022-04-21 13:13 ` ppalka at gcc dot gnu.org 2022-04-21 13:14 ` ppalka at gcc dot gnu.org 2022-04-22 5:53 ` 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-105297-4@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).