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++/102629] [10 Regression] ICE: tree check in lookup_base, at cp/search.c:233 since r10-2194-g10acaf4db9f8b54b
Date: Thu, 12 May 2022 21:23:13 +0000	[thread overview]
Message-ID: <bug-102629-4-fTSWd4wv3U@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102629-4@http.gcc.gnu.org/bugzilla/>

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

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

https://gcc.gnu.org/g:93ec7bf22530610ef697fd3a64a28bebd589c790

commit r10-10724-g93ec7bf22530610ef697fd3a64a28bebd589c790
Author: Jason Merrill <jason@redhat.com>
Date:   Tue Apr 26 00:19:40 2022 -0400

    c++: pack init-capture of unresolved overload [PR102629]

    Here we were failing to diagnose that the initializer for the capture pack
    is an unresolved overload.  It turns out that the reason we didn't
recognize
    the deduction failure in do_auto_deduction was that the individual 'auto'
in
    the expansion of the capture pack was still marked as a parameter pack, so
    we were deducing it to an empty pack instead of failing.

            PR c++/102629

    gcc/cp/ChangeLog:

            * pt.c (gen_elem_of_pack_expansion_instantiation): Clear
            TEMPLATE_TYPE_PARAMETER_PACK on auto.

    gcc/testsuite/ChangeLog:

            * g++.dg/cpp2a/lambda-pack-init7.C: New test.

  parent reply	other threads:[~2022-05-12 21:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-06 15:32 [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 hewillk at gmail dot com
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 ` cvs-commit at gcc dot gnu.org [this message]
2022-05-12 21:35 ` [Bug c++/102629] [10 " 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-fTSWd4wv3U@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).