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++/97399] [9/10/11 Regression] g++ 9.3 cannot compile SFINAE code with separated declaration and definition, g++ 7.3 compiles
Date: Sat, 23 Jan 2021 05:25:06 +0000	[thread overview]
Message-ID: <bug-97399-4-iM17QpYKlH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97399-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Patrick Palka <ppalka@gcc.gnu.org>:

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

commit r11-6878-ga8cef3cba6945730c69e15dcdad726e74b50fe58
Author: Patrick Palka <ppalka@redhat.com>
Date:   Sat Jan 23 00:24:17 2021 -0500

    c++: 'this' injection and static member functions [PR97399]

    In the testcase pr97399.C below, finish_qualified_id_expr at parse time
    adds an implicit 'this->' to the expression tmp::integral<T> (because
    it's type-dependent, and also current_class_ptr is set at this point)
    within the trailing return type.  Later when substituting into this
    trailing return type we crash because we can't resolve the 'this', since
    tsubst_function_type does inject_this_parm only for non-static member
    functions, which tmp::func is not.

    This patch fixes this issue by removing the type-dependence check
    in finish_qualified_id_expr added by r9-5972, and instead relaxes
    shared_member_p to handle dependent USING_DECLs:

    > I think I was wrong in my assertion around Alex's patch that
    > shared_member_p should abort on a dependent USING_DECL; it now seems
    > appropriate for it to return false if we don't know, we just need to
    > adjust the comment to say that.

    And when parsing a friend function declaration, we shouldn't be setting
    current_class_ptr at all, so this patch additionally suppresses
    inject_this_parm in this case.

    Finally, the self-contained change to cp_parser_init_declarator is so
    that we properly communicate static-ness to cp_parser_direct_declarator
    when parsing a member function template.  This lets us reject the
    explicit use of 'this' in the testcase this2.C below.

    gcc/cp/ChangeLog:

            PR c++/97399
            * cp-tree.h (shared_member_p): Adjust declaration.
            * parser.c (cp_parser_init_declarator): If the storage class
            specifier is sc_static, pass true for static_p to
            cp_parser_declarator.
            (cp_parser_direct_declarator): Don't do inject_this_parm when
            the declarator is a friend.
            * search.c (shared_member_p): Change return type to bool and
            adjust function body accordingly.  Return false for a dependent
            USING_DECL instead of aborting.
            * semantics.c (finish_qualified_id_expr): Rely on shared_member_p
            even when type-dependent.

    gcc/testsuite/ChangeLog:

            PR c++/88548
            PR c++/97399
            * g++.dg/cpp0x/this2.C: New test.
            * g++.dg/template/pr97399.C: New test.

  parent reply	other threads:[~2021-01-23  5:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-13  9:58 [Bug c++/97399] New: " renlin at gcc dot gnu.org
2020-10-13  9:58 ` [Bug c++/97399] " renlin at gcc dot gnu.org
2020-10-13 11:02 ` [Bug c++/97399] [9/10/11 Regression] " rguenth at gcc dot gnu.org
2020-10-13 14:10 ` marxin at gcc dot gnu.org
2021-01-14  9:25 ` rguenth at gcc dot gnu.org
2021-01-20 20:00 ` ppalka at gcc dot gnu.org
2021-01-23  5:25 ` cvs-commit at gcc dot gnu.org [this message]
2021-01-23  5:25 ` [Bug c++/97399] [9/10 " ppalka at gcc dot gnu.org
2021-04-10 20:33 ` cvs-commit at gcc dot gnu.org
2021-06-01  8:18 ` rguenth at gcc dot gnu.org
2022-05-27  9:43 ` [Bug c++/97399] [10 " rguenth at gcc dot gnu.org
2022-06-28 10:42 ` jakub at gcc dot gnu.org
2023-07-07  9:08 ` rguenth 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-97399-4-iM17QpYKlH@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).