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++/110463] [13/14 Regression] Mutable subobject is usable in a constant expression
Date: Thu, 29 Jun 2023 20:10:48 +0000	[thread overview]
Message-ID: <bug-110463-4-GHAP2bdVHi@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110463-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 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:fd8a1be04d4cdbfefea457b99ed8404d77b35dd6

commit r14-2198-gfd8a1be04d4cdbfefea457b99ed8404d77b35dd6
Author: Patrick Palka <ppalka@redhat.com>
Date:   Thu Jun 29 16:02:04 2023 -0400

    c++: unpropagated CONSTRUCTOR_MUTABLE_POISON [PR110463]

    Here we're incorrectly accepting the mutable member accesses because
    cp_fold neglects to propagate CONSTRUCTOR_MUTABLE_POISON when folding a
    CONSTRUCTOR.

            PR c++/110463

    gcc/cp/ChangeLog:

            * cp-gimplify.cc (cp_fold) <case CONSTRUCTOR>: Propagate
            CONSTRUCTOR_MUTABLE_POISON.

    gcc/testsuite/ChangeLog:

            * g++.dg/cpp0x/constexpr-mutable6.C: New test.

  parent reply	other threads:[~2023-06-29 20:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-28 17:15 [Bug c++/110463] New: " fchelnokov at gmail dot com
2023-06-28 17:29 ` [Bug c++/110463] [13/14 Regression] " ppalka at gcc dot gnu.org
2023-06-29 20:10 ` cvs-commit at gcc dot gnu.org [this message]
2023-07-01  1:28 ` cvs-commit at gcc dot gnu.org
2023-07-01  1:29 ` ppalka at gcc dot gnu.org
2023-07-01 18:06 ` fchelnokov at gmail dot com

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-110463-4-GHAP2bdVHi@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).