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++/108526] [13 Regression] ICE in start_preparsed_function with static on generic lambdas inside a template Date: Tue, 07 Mar 2023 19:34:19 +0000 [thread overview] Message-ID: <bug-108526-4-edz6qEvjcd@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108526-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108526 --- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The trunk branch has been updated by Jason Merrill <jason@gcc.gnu.org>: https://gcc.gnu.org/g:4f181f9c7ee3efc509d185fdfda33be9018f1611 commit r13-6533-g4f181f9c7ee3efc509d185fdfda33be9018f1611 Author: Jason Merrill <jason@redhat.com> Date: Mon Mar 6 21:36:28 2023 -0500 c++: static lambda tsubst [PR108526] A missed piece of the patch for static operator(): in tsubst_function_decl, we don't want to replace the first parameter with a new closure pointer if operator() is static. PR c++/108526 PR c++/106651 gcc/cp/ChangeLog: * pt.cc (tsubst_function_decl): Don't replace the closure parameter if DECL_STATIC_FUNCTION_P. gcc/testsuite/ChangeLog: * g++.dg/cpp23/static-operator-call5.C: Pass -g.
prev parent reply other threads:[~2023-03-07 19:34 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-24 17:50 [Bug c++/108526] New: [13 Regression] ICE in start_preparsed_function, at cp/decl.cc:17281 gscfq@t-online.de 2023-01-24 18:25 ` [Bug c++/108526] " pinskia at gcc dot gnu.org 2023-01-24 18:30 ` jakub at gcc dot gnu.org 2023-01-24 20:22 ` jason at gcc dot gnu.org 2023-01-24 22:12 ` [Bug c++/108526] [13 Regression] ICE in start_preparsed_function with static on generic lambdas inside a template cvs-commit at gcc dot gnu.org 2023-01-24 22:12 ` jason at gcc dot gnu.org 2023-03-07 19:34 ` cvs-commit at gcc dot gnu.org [this message]
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-108526-4-edz6qEvjcd@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).