public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/97358] New: [8/9/10/11 Regression] ICE while building firefox since r8-2720 Date: Fri, 09 Oct 2020 19:11:11 +0000 [thread overview] Message-ID: <bug-97358-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97358 Bug ID: 97358 Summary: [8/9/10/11 Regression] ICE while building firefox since r8-2720 Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: jakub at gcc dot gnu.org Target Milestone: --- The following testcase reduced from firefox ICEs with -std=c++17 starting with r8-2720-gf44a8dd56f5bfbd0596c39693e268ef880c06221 (before it has been rejected). clang++ accepts it, though unsure if the reduction didn't make it invalid (or whether the original 13MB+ :( testcase is valid). struct A; struct B { A foo (); }; enum C { E }; struct A { template <typename... T> void bar (T... x) { auto v {[x...] { x; }...}; } }; template <typename, C> using F = B; struct G { F<int, E> baz (); }; enum H { J }; struct D { using K = G; }; template <H> struct I : D { void qux (); }; template <H h> void I<h>::qux () { K a; a.baz ().foo ().bar (); } template class I<J>;
next reply other threads:[~2020-10-09 19:11 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-09 19:11 jakub at gcc dot gnu.org [this message] 2020-10-09 19:11 ` [Bug c++/97358] " jakub at gcc dot gnu.org 2020-10-09 19:32 ` jakub at gcc dot gnu.org 2020-10-12 6:23 ` rguenth at gcc dot gnu.org 2020-10-12 9:42 ` jakub at gcc dot gnu.org 2020-10-12 10:29 ` jakub at gcc dot gnu.org 2020-10-14 15:23 ` jakub at gcc dot gnu.org 2020-10-14 15:34 ` sumbera at volny dot cz 2020-10-14 15:41 ` jakub at gcc dot gnu.org 2020-10-14 18:17 ` ppalka at gcc dot gnu.org 2020-10-14 18:19 ` ppalka at gcc dot gnu.org 2020-10-14 18:27 ` jakub at gcc dot gnu.org 2020-10-14 18:44 ` jason at gcc dot gnu.org 2020-10-14 18:48 ` jason at gcc dot gnu.org 2020-10-14 19:24 ` jakub at gcc dot gnu.org 2020-10-14 19:44 ` cvs-commit at gcc dot gnu.org 2020-10-14 19:47 ` [Bug c++/97358] [8/9/10 " jason at gcc dot gnu.org 2020-10-14 20:15 ` jakub at gcc dot gnu.org 2020-10-15 7:16 ` dan at danny dot cz 2020-10-15 7:42 ` jakub at gcc dot gnu.org 2020-10-15 8:24 ` sumbera at volny dot cz 2020-10-15 8:42 ` dan at danny dot cz 2020-10-16 0:32 ` richard-gccbugzilla at metafoo dot co.uk 2021-05-14 9:53 ` [Bug c++/97358] [9/10 " jakub at gcc dot gnu.org 2021-06-01 8:18 ` rguenth at gcc dot gnu.org 2022-05-27 9:43 ` [Bug c++/97358] [10 " rguenth at gcc dot gnu.org 2022-06-28 10:42 ` jakub at gcc dot gnu.org 2023-07-07 9:07 ` rguenth 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-97358-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).