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++/105541] [12 Regression] ICE: Segmentation fault when template lambda in requires-clause
Date: Fri, 01 Jul 2022 14:56:11 +0000	[thread overview]
Message-ID: <bug-105541-4-5NwVN7RIpq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105541-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 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:b1c8ee2627696717013ebdb1ca3f5f97a76b1cb9

commit r12-8535-gb1c8ee2627696717013ebdb1ca3f5f97a76b1cb9
Author: Jason Merrill <jason@redhat.com>
Date:   Wed May 11 14:53:26 2022 -0400

    c++: lambda template in requires [PR105541]

    Since the patch for PR103408, the template parameters for the lambda in
this
    test have level 1 instead of 2, and we were treating null template args as
1
    level of arguments, so tsubst_template_parms decided it had nothing to do.
    Fixed by distinguishing between <> and no args at all, which is what we
have
    in our "substitution" in a requires-expression.

            PR c++/105541

    gcc/cp/ChangeLog:

            * cp-tree.h (TMPL_ARGS_DEPTH): 0 for null args.
            * parser.cc (cp_parser_enclosed_template_argument_list):
            Use 0-length TREE_VEC for <>.

    gcc/testsuite/ChangeLog:

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

  parent reply	other threads:[~2022-07-01 14:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-10  2:24 [Bug c++/105541] New: " hewillk at gmail dot com
2022-05-10  2:26 ` [Bug c++/105541] " hewillk at gmail dot com
2022-05-10  7:50 ` [Bug c++/105541] [12/13 Regression] " rguenth at gcc dot gnu.org
2022-05-10 13:46 ` mpolacek at gcc dot gnu.org
2022-05-10 22:18 ` jason at gcc dot gnu.org
2022-05-10 22:22 ` jason at gcc dot gnu.org
2022-05-11 19:30 ` cvs-commit at gcc dot gnu.org
2022-07-01 14:56 ` cvs-commit at gcc dot gnu.org [this message]
2022-07-01 14:57 ` [Bug c++/105541] [12 " jason at gcc dot gnu.org
2023-05-25 13:10 ` 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-105541-4-5NwVN7RIpq@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).