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++/105268] type/value mismatch when using variadic concept
Date: Fri, 15 Apr 2022 15:35:30 +0000	[thread overview]
Message-ID: <bug-105268-4-XsxMCtHE7Z@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105268-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The trunk branch has been updated by Marek Polacek <mpolacek@gcc.gnu.org>:

https://gcc.gnu.org/g:ccae4443c8322d9d82a19a1e7c689413a122a478

commit r12-8176-gccae4443c8322d9d82a19a1e7c689413a122a478
Author: Marek Polacek <polacek@redhat.com>
Date:   Thu Apr 14 13:48:15 2022 -0400

    c++: wrong error with variadic concept [PR105268]

    Here we issue a wrong error for the

      template<typename T = S<C_many<int>>> void g();

    line in the testcase.  I surmise that's because we mistakenly parse
    C_many<int> as a placeholder-type-specifier, and things go wrong from
    there.  We are in a default argument so we should reject parsing
C_many<int>
    as a placeholder-type-specifier, which would mean creating a new parameter.
    We want C_many<int> to be a concept-id instead.

    It's interesting to see why the same problem didn't occur for C_one<int>.
    In that case, cp_parser_placeholder_type_specifier ->
finish_type_constraints
    -> build_type_constraint -> build_concept_check -> build_standard_check ->
    coerce_template_parms fails the parse here:

     8916   nargs = inner_args ? NUM_TMPL_ARGS (inner_args) : 0;
     8917   if ((nargs - variadic_args_p > nparms && !variadic_p)
     8918       || (nargs < nparms - variadic_p
     8919           && require_all_args
     8920           && !variadic_args_p
     8921           && (!use_default_args
     8922               || (TREE_VEC_ELT (parms, nargs) != error_mark_node
     8923                   && !TREE_PURPOSE (TREE_VEC_ELT (parms, nargs))))))
     8924     {
     8925     bad_nargs:
     ...
     8943       return error_mark_node;

    because nargs is 2 (the targs are <WILDCARD_DECL, int>) while nparms is
    1 (for the one 'typename' in the tparam list of C_one).  But for
    C_many<int> variadic_p is true so we don't return error_mark_node but
    <type_argument_pack>.

    This patch does not issue any error for the !tentative case because
    I didn't figure out how to trigger that.  So it adds an assert instead.

            PR c++/105268

    gcc/cp/ChangeLog:

            * parser.cc (cp_parser_placeholder_type_specifier): Return
            error_mark_node when trying to build up a constrained parameter in
            a default argument.

    gcc/testsuite/ChangeLog:

            * g++.dg/concepts/variadic6.C: New test.

  parent reply	other threads:[~2022-04-15 15:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-13 23:05 [Bug c++/105268] New: " barry.revzin at gmail dot com
2022-04-13 23:08 ` [Bug c++/105268] " mpolacek at gcc dot gnu.org
2022-04-14  2:05 ` mpolacek at gcc dot gnu.org
2022-04-14 17:29 ` mpolacek at gcc dot gnu.org
2022-04-15 15:35 ` cvs-commit at gcc dot gnu.org [this message]
2022-04-15 15:36 ` mpolacek 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-105268-4-XsxMCtHE7Z@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).