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++/110106] [11/12/13/14 Regression] ICE on noexcept(noexcept(...)) with optional
Date: Fri, 21 Jul 2023 17:52:44 +0000	[thread overview]
Message-ID: <bug-110106-4-9uLwpJNFY3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110106-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 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:e36d1994051122fc6e1f8c728fbd109a59e0a822

commit r14-2717-ge36d1994051122fc6e1f8c728fbd109a59e0a822
Author: Marek Polacek <polacek@redhat.com>
Date:   Tue Jul 18 16:02:21 2023 -0400

    c++: fix ICE with is_really_empty_class [PR110106]

    is_really_empty_class is liable to crash when it gets an incomplete
    or dependent type.  Since r11-557, we pass the yet-uninstantiated
    class type S<0> of the PARM_DECL s to is_really_empty_class -- because
    of the potential_rvalue_constant_expression ->
is_rvalue_constant_expression
    change in cp_parser_constant_expression.  Here we're not parsing
    a template so we did not check COMPLETE_TYPE_P as we should.

    It should work to complete the type before checking COMPLETE_TYPE_P.

            PR c++/110106

    gcc/cp/ChangeLog:

            * constexpr.cc (potential_constant_expression_1): Try to complete
the
            type when !processing_template_decl.

    gcc/testsuite/ChangeLog:

            * g++.dg/cpp0x/noexcept80.C: New test.

  parent reply	other threads:[~2023-07-21 17:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-03 18:18 [Bug c++/110106] New: " stevenxia990430 at gmail dot com
2023-06-03 18:29 ` [Bug c++/110106] [11/12/13/14 Regression] " pinskia at gcc dot gnu.org
2023-06-03 19:31 ` pinskia at gcc dot gnu.org
2023-06-03 19:34 ` pinskia at gcc dot gnu.org
2023-06-05  6:46 ` rguenth at gcc dot gnu.org
2023-06-05 15:28 ` mpolacek at gcc dot gnu.org
2023-07-18 20:01 ` mpolacek at gcc dot gnu.org
2023-07-21 17:52 ` cvs-commit at gcc dot gnu.org [this message]
2023-12-12  0:37 ` [Bug c++/110106] [11/12/13 " cvs-commit at gcc dot gnu.org
2023-12-12  0:38 ` [Bug c++/110106] [11/12 " 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-110106-4-9uLwpJNFY3@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).