public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/101099] New: [9/10/11/12 Regression] ICE in type_unification_real, at cp/pt.c:22173 Date: Wed, 16 Jun 2021 17:21:16 +0000 [thread overview] Message-ID: <bug-101099-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101099 Bug ID: 101099 Summary: [9/10/11/12 Regression] ICE in type_unification_real, at cp/pt.c:22173 Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: gscfq@t-online.de Target Milestone: --- Started with r9 between and 20190615 and 20190727, r8 accepts it. With options -std=gnu++11 -fconcepts and several testsuite files or the following variant : $ cat z1.cc #include <initializer_list> constexpr auto list = { 1, 2, 3 }; $ g++-8 -c z1.cc -std=gnu++11 -fconcepts $ $ g++-12-20210613 -c z1.cc -std=gnu++11 -fconcepts z1.cc:2:33: internal compiler error: in type_unification_real, at cp/pt.c:22173 2 | constexpr auto list = { 1, 2, 3 }; | ^ 0x8313d8 type_unification_real ../../gcc/cp/pt.c:22173 0x819606 do_auto_deduction(tree_node*, tree_node*, tree_node*, int, auto_deduction_context, tree_node*, int) ../../gcc/cp/pt.c:29619 0x745bf6 cp_finish_decl(tree_node*, tree_node*, bool, tree_node*, int) ../../gcc/cp/decl.c:7834 0x802791 cp_parser_init_declarator ../../gcc/cp/parser.c:22044 0x7e348a cp_parser_simple_declaration ../../gcc/cp/parser.c:14587 0x8081f5 cp_parser_declaration ../../gcc/cp/parser.c:14284 0x80770b cp_parser_translation_unit ../../gcc/cp/parser.c:4942 0x80770b c_parse_file() ../../gcc/cp/parser.c:45611 0x8d7412 c_common_parse_file() ../../gcc/c-family/c-opts.c:1219
next reply other threads:[~2021-06-16 17:21 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-16 17:21 gscfq@t-online.de [this message] 2021-06-17 6:38 ` [Bug c++/101099] " rguenth at gcc dot gnu.org 2021-06-17 9:32 ` marxin at gcc dot gnu.org 2021-10-02 7:21 ` pinskia at gcc dot gnu.org 2022-01-17 14:32 ` rguenth at gcc dot gnu.org 2022-05-27 9:45 ` [Bug c++/101099] [10/11/12/13 " rguenth at gcc dot gnu.org 2022-06-28 10:45 ` jakub at gcc dot gnu.org 2023-02-09 22:07 ` mpolacek at gcc dot gnu.org 2023-02-10 8:31 ` marxin at gcc dot gnu.org 2023-02-10 15:14 ` mpolacek at gcc dot gnu.org 2023-07-07 10:40 ` [Bug c++/101099] [11/12/13/14 " 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-101099-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).