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++/108242] [10/11/12 Regression] '__FUNCTION__' was not declared when used inside a generic (templated) lambda declared inside a template function
Date: Tue, 18 Apr 2023 20:46:07 +0000	[thread overview]
Message-ID: <bug-108242-4-N2MAiEJCH6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108242-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108242

--- Comment #9 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:890d711a2477119a34cf435f6159b6253b124374

commit r12-9437-g890d711a2477119a34cf435f6159b6253b124374
Author: Jason Merrill <jason@redhat.com>
Date:   Thu Mar 16 15:11:25 2023 -0400

    c++: generic lambda, local class, __func__ [PR108242]

    Here we are trying to do name lookup in a deferred instantiation of t() and
    failing to find __func__.  tsubst_expr already tries to instantiate members
    of local classes, but was failing with the partial instantiation of generic
    lambdas.

            PR c++/108242

    gcc/cp/ChangeLog:

            * pt.cc (tsubst_expr) [TAG_DEFN]: Handle partial instantiation.

    gcc/testsuite/ChangeLog:

            * g++.dg/cpp1y/lambda-generic-func2.C: New test.

  parent reply	other threads:[~2023-04-18 20:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-28 16:13 [Bug c++/108242] New: '__FUNCTION__' was not declared when used inside a " n.eugene536 at gmail dot com
2022-12-28 17:50 ` [Bug c++/108242] '__FUNCTION__' was not declared when used inside a generic (templated) " pinskia at gcc dot gnu.org
2022-12-28 17:54 ` [Bug c++/108242] [10/11/12/13 Regression] " pinskia at gcc dot gnu.org
2022-12-29  2:44 ` pinskia at gcc dot gnu.org
2023-01-02  9:27 ` jakub at gcc dot gnu.org
2023-01-09 14:03 ` rguenth at gcc dot gnu.org
2023-02-03 18:09 ` jakub at gcc dot gnu.org
2023-02-03 18:16 ` mpolacek at gcc dot gnu.org
2023-02-03 18:23 ` jakub at gcc dot gnu.org
2023-03-16 19:15 ` jason at gcc dot gnu.org
2023-03-16 22:11 ` cvs-commit at gcc dot gnu.org
2023-04-18 20:46 ` cvs-commit at gcc dot gnu.org [this message]
2023-07-07 10:44 ` [Bug c++/108242] [11 " 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-108242-4-N2MAiEJCH6@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: link
Be 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).