public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "janezz55 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/105064] requires crashes gcc Date: Sun, 27 Mar 2022 19:16:02 +0000 [thread overview] Message-ID: <bug-105064-4-8nUrDZ2yDy@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105064-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105064 --- Comment #9 from Janez Zemva <janezz55 at gmail dot com> --- Anyway, I've grown bored, so here's the minimal test case: #include <type_traits> class task { friend void suspend_to(auto const tp) noexcept requires(std::is_same_v<task* const, decltype(tp)>); }; class loop { friend void suspend_to(auto const tp) noexcept requires(std::is_same_v<task* const, decltype(tp)>); }; void suspend_to(auto const tp) noexcept requires(std::is_same_v<task* const, decltype(tp)>) { } $ g++ -std=c++20 -Ofast tmp.cpp -o t tmp.cpp:12:55: internal compiler error: Segmentation fault 12 | requires(std::is_same_v<task* const, decltype(tp)>); | ^ 0xe4c988 internal_error(char const*, ...) ???:0 0xf778a4 duplicate_decls(tree_node*, tree_node*, bool, bool) ???:0 0xf82c3b pushdecl_namespace_level(tree_node*, bool) ???:0 0x10ecbfe push_template_decl(tree_node*, bool) ???:0 0x159b601 do_friend(tree_node*, tree_node*, tree_node*, tree_node*, overload_flags, bool) ???:0 0x1001717 grokdeclarator(cp_declarator const*, cp_decl_specifier_seq*, decl_context, int, tree_node**) ???:0 0x105cc75 grokfield(cp_declarator const*, cp_decl_specifier_seq*, tree_node*, bool, tree_node*, tree_node*) ???:0 0x14e7873 c_parse_file() ???:0 0x14c9d9e c_common_parse_file() ???:0 Please submit a full bug report, with preprocessed source if appropriate. Please include the complete backtrace with any bug report. See <https://bugs.archlinux.org/> for instructions.
next prev parent reply other threads:[~2022-03-27 19:16 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-26 17:21 [Bug c++/105064] New: " janezz55 at gmail dot com 2022-03-26 20:40 ` [Bug c++/105064] " redi at gcc dot gnu.org 2022-03-27 11:43 ` janezz55 at gmail dot com 2022-03-27 13:00 ` redi at gcc dot gnu.org 2022-03-27 13:02 ` redi at gcc dot gnu.org 2022-03-27 18:01 ` janezz55 at gmail dot com 2022-03-27 18:05 ` janezz55 at gmail dot com 2022-03-27 18:29 ` janezz55 at gmail dot com 2022-03-27 18:39 ` janezz55 at gmail dot com 2022-03-27 19:16 ` janezz55 at gmail dot com [this message] 2022-03-27 22:19 ` [Bug c++/105064] [10/11/12 Regression] " redi at gcc dot gnu.org 2022-03-28 7:30 ` rguenth at gcc dot gnu.org 2022-03-28 13:27 ` ppalka at gcc dot gnu.org 2022-03-28 18:17 ` cvs-commit at gcc dot gnu.org 2022-03-28 18:19 ` [Bug c++/105064] [10/11 " ppalka at gcc dot gnu.org 2022-04-07 19:19 ` cvs-commit at gcc dot gnu.org 2022-05-04 0:24 ` [Bug c++/105064] [10 " ppalka 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-105064-4-8nUrDZ2yDy@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).