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++/95562] [10/11 Regression] ICE when using noexcept depending on boolean template parameter since r10-1280-g78f7607db4c53f8c
Date: Wed, 10 Jun 2020 13:36:39 +0000	[thread overview]
Message-ID: <bug-95562-4-NZ3TYyCYN4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95562-4@http.gcc.gnu.org/bugzilla/>

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

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

https://gcc.gnu.org/g:4fed5d5dd85e3f5d812d125f692351646a0417cb

commit r11-1176-g4fed5d5dd85e3f5d812d125f692351646a0417cb
Author: Marek Polacek <polacek@redhat.com>
Date:   Tue Jun 9 18:08:45 2020 -0400

    c++: Fix ICE with delayed parsing of noexcept-specifier [PR95562]

    Here we ICE because a DEFERRED_PARSE expression leaked to tsubst_copy.
    We create these expressions for deferred noexcept-specifiers in
    cp_parser_save_noexcept; they are supposed to be re-parsed in
    cp_parser_late_noexcept_specifier.  In this case we never got around
    to re-parsing it because the noexcept-specifier was attached to a
    pointer to a function, not to a function declaration.  But we should
    not have delayed the parsing here in the first place; we already
    avoid delaying the parsing for alias-decls, typedefs, and friend
    function declarations.  (Clang++ also doesn't delay the parsing
    for pointers to function.)

    gcc/cp/ChangeLog:

            PR c++/95562
            * parser.c (cp_parser_direct_declarator): Clear
            CP_PARSER_FLAGS_DELAY_NOEXCEPT if the declarator kind is not
            cdk_id.

    gcc/testsuite/ChangeLog:

            PR c++/95562
            * g++.dg/cpp0x/noexcept60.C: New test.

  parent reply	other threads:[~2020-06-10 13:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-06 13:19 [Bug c++/95562] New: ICE when using noexcept depending on boolean template parameter philipp.koegel at mailbox dot org
2020-06-09 11:28 ` [Bug c++/95562] [10/11 Regression] ICE when using noexcept depending on boolean template parameter since r10-1280-g78f7607db4c53f8c marxin at gcc dot gnu.org
2020-06-09 13:21 ` mpolacek at gcc dot gnu.org
2020-06-09 22:05 ` mpolacek at gcc dot gnu.org
2020-06-10 13:36 ` cvs-commit at gcc dot gnu.org [this message]
2020-06-10 15:33 ` cvs-commit at gcc dot gnu.org
2020-06-10 15:34 ` mpolacek at gcc dot gnu.org
2020-06-15 16:19 ` 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-95562-4-NZ3TYyCYN4@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).