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++/103186] [11/12 Regression] ICE with lambda as default argument in template
Date: Tue, 01 Feb 2022 19:15:46 +0000	[thread overview]
Message-ID: <bug-103186-4-uft8COZFO4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103186-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #13 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jason Merrill <jason@gcc.gnu.org>:

https://gcc.gnu.org/g:8a3789786205376e3ba19fdefadd8937e8ac534e

commit r12-6973-g8a3789786205376e3ba19fdefadd8937e8ac534e
Author: Jason Merrill <jason@redhat.com>
Date:   Wed Jan 26 16:42:57 2022 -0500

    c++: lambda in template default argument [PR103186]

    The problem with this testcase was that since my patch for PR97900 we
    weren't preserving DECL_UID identity for parameters of instantiations of
    templated functions, so using those parameters as the keys for the
    defarg_inst map broke.  I think this was always fragile given the
    possibility of redeclarations, so instead of reverting that change let's
    switch to keying off the function.

    Memory use compiling stdc++.h is not noticeably different.

            PR c++/103186

    gcc/cp/ChangeLog:

            * pt.cc (defarg_inst): Use tree_vec_map_cache_hasher.
            (defarg_insts_for): New.
            (tsubst_default_argument): Adjust.

    gcc/testsuite/ChangeLog:

            * g++.dg/cpp0x/lambda/lambda-defarg10.C: New test.

  parent reply	other threads:[~2022-02-01 19:15 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-11 10:06 [Bug c++/103186] New: redefinition of template symbol error with strange error diagnostic dl.soluz at gmx dot net
2021-11-11 10:13 ` [Bug c++/103186] " dl.soluz at gmx dot net
2021-11-11 10:13 ` dl.soluz at gmx dot net
2021-11-11 10:21 ` pinskia at gcc dot gnu.org
2021-11-11 10:25 ` dl.soluz at gmx dot net
2021-11-11 10:36 ` dl.soluz at gmx dot net
2021-11-11 10:38 ` pinskia at gcc dot gnu.org
2021-11-11 10:41 ` [Bug c++/103186] [11/12 Regression] " pinskia at gcc dot gnu.org
2021-11-11 13:11 ` [Bug c++/103186] [11/12 Regression] ICE with fold-expression and lambdas as default rguenth at gcc dot gnu.org
2021-11-12 18:55 ` [Bug c++/103186] [11/12 Regression] ICE with fold-expression and lambdas as default since r11-7965-g23be03a0f243a084 marxin at gcc dot gnu.org
2021-12-07  1:00 ` [Bug c++/103186] [11/12 Regression] ICE with " pinskia at gcc dot gnu.org
2021-12-07  1:01 ` pinskia at gcc dot gnu.org
2021-12-30 13:48 ` pinskia at gcc dot gnu.org
2022-01-07  8:49 ` pinskia at gcc dot gnu.org
2022-01-26 19:37 ` [Bug c++/103186] [11/12 Regression] ICE with lambda as default argument in template jason at gcc dot gnu.org
2022-02-01 19:15 ` cvs-commit at gcc dot gnu.org [this message]
2022-02-01 19:17 ` [Bug c++/103186] [11 " jason at gcc dot gnu.org
2022-03-22  5:18 ` cvs-commit at gcc dot gnu.org
2022-04-12 17:28 ` jason at gcc dot gnu.org
2022-07-20 15:11 ` redi 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-103186-4-uft8COZFO4@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).