public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hewillk at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/102629] New: internal compiler error: tree check: expected record_type or union_type or qual_union_type, have decltype_type in lookup_base, at cp/search.c:233 Date: Wed, 06 Oct 2021 15:32:19 +0000 [thread overview] Message-ID: <bug-102629-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102629 Bug ID: 102629 Summary: internal compiler error: tree check: expected record_type or union_type or qual_union_type, have decltype_type in lookup_base, at cp/search.c:233 Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: hewillk at gmail dot com Target Milestone: --- 12 Regression: #include <utility> struct S {}; template <typename... Args> void foo(Args&&... args) { [...args = std::forward<Args> /*(args)*/] { [](auto...) { } (std::forward<Args>(args)...); }; } void bar( ) { foo(S{}); } https://godbolt.org/z/WhnWTbvoj
next reply other threads:[~2021-10-06 15:32 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-06 15:32 hewillk at gmail dot com [this message] 2021-10-11 9:53 ` [Bug c++/102629] ICE: tree check: expected record_type or union_type or qual_union_type, have decltype_type in lookup_base, at cp/search.c:233 since r10-2194-g10acaf4db9f8b54b marxin at gcc dot gnu.org 2021-10-17 20:12 ` [Bug c++/102629] [10/11/12 Regression] ICE: tree check " pinskia at gcc dot gnu.org 2022-03-31 16:52 ` mpolacek at gcc dot gnu.org 2022-04-26 4:18 ` jason at gcc dot gnu.org 2022-04-26 20:12 ` cvs-commit at gcc dot gnu.org 2022-05-12 20:14 ` [Bug c++/102629] [10/11 " cvs-commit at gcc dot gnu.org 2022-05-12 21:23 ` [Bug c++/102629] [10 " cvs-commit at gcc dot gnu.org 2022-05-12 21:35 ` jason at gcc dot gnu.org 2022-05-25 17:03 ` jason 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-102629-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).