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++/103706] [11 Regression] ICE: tree check: accessed elt 1 of 'tree_vec' with 0 elts in hash, at cp/constraint.cc:2503 Date: Tue, 12 Apr 2022 23:44:25 +0000 [thread overview] Message-ID: <bug-103706-4-9SK6lOcSYA@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103706-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103706 --- Comment #10 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by Patrick Palka <ppalka@gcc.gnu.org>: https://gcc.gnu.org/g:6eb8eb51a827a349cd6acce5f16ffef31d8934b1 commit r11-9842-g6eb8eb51a827a349cd6acce5f16ffef31d8934b1 Author: Patrick Palka <ppalka@redhat.com> Date: Tue Feb 8 08:46:13 2022 -0500 c++: constrained auto in lambda using outer tparms [PR103706] Here we're crashing during satisfaction of the lambda's placeholder type constraints because the constraints depend on the template arguments from the enclosing scope, which aren't part of the lambda's DECL_TI_ARGS. This patch fixes this by making do_auto_deduction consider the "regenerating" template arguments of a lambda for satisfaction, mirroring what's done in satisfy_declaration_constraints. PR c++/103706 gcc/cp/ChangeLog: * constraint.cc (satisfy_declaration_constraints): Use lambda_regenerating_args instead. * cp-tree.h (lambda_regenerating_args): Declare. * pt.c (lambda_regenerating_args): Define, split out from satisfy_declaration_constraints. (do_auto_deduction): Use lambda_regenerating_args to obtain the full set of outer template arguments for satisfaction when inside a lambda. gcc/testsuite/ChangeLog: * g++.dg/cpp2a/concepts-lambda18.C: New test. (cherry picked from commit 34ba3d9a2bf72742b1c150a2dd17d10e3e3f0964)
next prev parent reply other threads:[~2022-04-12 23:44 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-14 7:51 [Bug c++/103706] New: [11/12 " asolokha at gmx dot com 2021-12-14 7:59 ` [Bug c++/103706] " pinskia at gcc dot gnu.org 2021-12-14 8:08 ` asolokha at gmx dot com 2021-12-14 8:09 ` pinskia at gcc dot gnu.org 2021-12-14 8:09 ` pinskia at gcc dot gnu.org 2022-01-31 16:28 ` ppalka at gcc dot gnu.org 2022-01-31 16:28 ` ppalka at gcc dot gnu.org 2022-02-08 13:48 ` cvs-commit at gcc dot gnu.org 2022-02-08 13:48 ` cvs-commit at gcc dot gnu.org 2022-02-08 13:55 ` [Bug c++/103706] [11 " ppalka at gcc dot gnu.org 2022-02-08 13:55 ` ppalka at gcc dot gnu.org 2022-04-12 23:44 ` cvs-commit at gcc dot gnu.org 2022-04-12 23:44 ` cvs-commit at gcc dot gnu.org [this message] 2022-04-12 23:46 ` ppalka 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-103706-4-9SK6lOcSYA@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).