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++/96082] [9/10 Regression] GCC rejects the template disambiguator with "typename"
Date: Tue, 04 Aug 2020 18:17:45 +0000	[thread overview]
Message-ID: <bug-96082-4-9QZD7oBnXP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96082-4@http.gcc.gnu.org/bugzilla/>

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

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

https://gcc.gnu.org/g:1c4d223d37d067f5d372688c0c0cc5a05d977df7

commit r10-8576-g1c4d223d37d067f5d372688c0c0cc5a05d977df7
Author: Marek Polacek <polacek@redhat.com>
Date:   Tue Aug 4 09:35:25 2020 -0400

    c++: Template keyword following :: [PR96082]

    In r9-4235 I tried to make sure that the template keyword follows
    a nested-name-specifier.  :: is a valid nested-name-specifier, so
    I also have to check 'globalscope' before giving the error.

    gcc/cp/ChangeLog:

            PR c++/96082
            * parser.c (cp_parser_elaborated_type_specifier): Allow
            'template' following ::.

    gcc/testsuite/ChangeLog:

            PR c++/96082
            * g++.dg/template/template-keyword3.C: New test.

    (cherry picked from commit 97def1f34c134d78d4423e9ac3e9b262417ea390)

  parent reply	other threads:[~2020-08-04 18:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-06 15:59 [Bug c++/96082] New: " haoxintu at gmail dot com
2020-07-07  7:22 ` [Bug c++/96082] [9/10/11 Regression] " rguenth at gcc dot gnu.org
2020-07-07  8:52 ` marxin at gcc dot gnu.org
2020-08-03 23:59 ` mpolacek at gcc dot gnu.org
2020-08-04 17:41 ` cvs-commit at gcc dot gnu.org
2020-08-04 18:17 ` cvs-commit at gcc dot gnu.org [this message]
2020-08-04 18:24 ` [Bug c++/96082] [9 " 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-96082-4-9QZD7oBnXP@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).