public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/105652] [12/13 Regression] ICE: in is_base_type, at dwarf2out.cc:13400 since r12-1937-gc28e1d288ab727de Date: Tue, 31 May 2022 19:32:00 +0000 [thread overview] Message-ID: <bug-105652-4-e4u212xfkM@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105652-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105652 --- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-12 branch has been updated by Jason Merrill <jason@gcc.gnu.org>: https://gcc.gnu.org/g:102a1472ab393c89bd74c06ff92bef55fa61812c commit r12-8443-g102a1472ab393c89bd74c06ff92bef55fa61812c Author: Jason Merrill <jason@redhat.com> Date: Thu May 26 22:43:05 2022 -0400 c++: lambda in concept [PR105652] We currently check satisfaction in the context of the constrained declaration (which may be wrong, see PR104111). When checking C<int> for S<int>, we currently substitute into the lambda in the context of S<T> (rather than S<int>, which seems wrong if the above isn't wrong), so the new closure type thinks its context is S<T>, which confuses debug output. For the moment, let's work around all of this by overriding the context of the closure. PR c++/105652 gcc/cp/ChangeLog: * pt.cc (tsubst_lambda_expr): Don't let a namespace-scope lambda instantiate into a class-scope lambda. gcc/testsuite/ChangeLog: * g++.dg/cpp2a/concepts-lambda20.C: New test.
next prev parent reply other threads:[~2022-05-31 19:32 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-19 5:35 [Bug c++/105652] New: ICE: in is_base_type, at dwarf2out.cc:13400 hewillk at gmail dot com 2022-05-19 6:21 ` [Bug c++/105652] " rguenth at gcc dot gnu.org 2022-05-19 7:13 ` hewillk at gmail dot com 2022-05-19 8:20 ` [Bug c++/105652] [12/13 Regression] ICE: in is_base_type, at dwarf2out.cc:13400 since r12-1937-gc28e1d288ab727de marxin at gcc dot gnu.org 2022-05-20 7:02 ` rguenth at gcc dot gnu.org 2022-05-27 2:39 ` jason at gcc dot gnu.org 2022-05-28 3:44 ` cvs-commit at gcc dot gnu.org 2022-05-31 19:32 ` cvs-commit at gcc dot gnu.org [this message] 2022-05-31 19:32 ` jason at gcc dot gnu.org 2024-04-13 8:03 ` pinskia 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-105652-4-e4u212xfkM@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).