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++/114426] [14 regression] ICE when building log4cxx on arm (cxx_eval_call_expression, at cp/constexpr.cc:3242) since r14-6507
Date: Fri, 12 Apr 2024 17:58:07 +0000	[thread overview]
Message-ID: <bug-114426-4-r6EwUP3FVS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114426-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #12 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:

https://gcc.gnu.org/g:0fd824d717ca901319864a5eeba4e62b278f8329

commit r14-9942-g0fd824d717ca901319864a5eeba4e62b278f8329
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Fri Apr 12 19:57:04 2024 +0200

    c++: Diagnose or avoid constexpr dtors in classes with virtual bases
[PR114426]

    I had another look at this P1 PR today.
    You said in the "c++: fix in-charge parm in constexpr" mail back in
December
    (as well as in the r14-6507 commit message):
    "Since a class with vbases can't have constexpr 'tors there isn't actually
    a need for an in-charge parameter in a destructor" but the ICE is because
    the destructor is marked implicitly constexpr.
    https://eel.is/c++draft/dcl.constexpr#3.2 says that a destructor of a class
    with virtual bases is not constexpr-suitable, but we were actually
    implementing this just for constructors, so clearly my fault from the
    https://wg21.link/P0784R7 implementation.  That paper clearly added that
    sentence in there and removed similar sentence just from the constructor
case.

    So, the following patch makes sure the
      else if (CLASSTYPE_VBASECLASSES (DECL_CONTEXT (fun)))
        {
          ret = false;
          if (complain)
            error ("%q#T has virtual base classes", DECL_CONTEXT (fun));
        }
    hunk is done no just for DECL_CONSTRUCTOR_P (fun), but also
    DECL_DESTRUCTOR_P (fun) - in that case just for cxx_dialect >= cxx20,
    as for cxx_dialect < cxx20 we already set ret = false; and diagnose
    a different error, so no need to diagnose two.

    2024-04-12  Jakub Jelinek  <jakub@redhat.com>

            PR c++/114426
            * constexpr.cc (is_valid_constexpr_fn): Return false/diagnose with
            complain destructors in classes with virtual bases.

            * g++.dg/cpp2a/pr114426.C: New test.
            * g++.dg/cpp2a/constexpr-dtor16.C: New test.

  parent reply	other threads:[~2024-04-12 17:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-22  5:11 [Bug c++/114426] New: [14 regression] ICE when building log4cxx on arm (cxx_eval_call_expression, at cp/constexpr.cc:3242) sjames at gcc dot gnu.org
2024-03-22  5:12 ` [Bug c++/114426] " sjames at gcc dot gnu.org
2024-03-22  5:13 ` sjames at gcc dot gnu.org
2024-03-22  5:14 ` sjames at gcc dot gnu.org
2024-03-22  6:51 ` rguenth at gcc dot gnu.org
2024-03-22  7:26 ` pinskia at gcc dot gnu.org
2024-03-22  8:01 ` sjames at gcc dot gnu.org
2024-03-22 12:36 ` law at gcc dot gnu.org
2024-03-22 15:11 ` [Bug c++/114426] [14 regression] ICE when building log4cxx on arm (cxx_eval_call_expression, at cp/constexpr.cc:3242) since r14-6507 jakub at gcc dot gnu.org
2024-03-22 15:50 ` jakub at gcc dot gnu.org
2024-03-22 15:52 ` jakub at gcc dot gnu.org
2024-03-23  8:06 ` jakub at gcc dot gnu.org
2024-04-10  8:02 ` rguenth at gcc dot gnu.org
2024-04-12  9:59 ` jakub at gcc dot gnu.org
2024-04-12 17:58 ` cvs-commit at gcc dot gnu.org [this message]
2024-04-12 17:58 ` jakub 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-114426-4-r6EwUP3FVS@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).