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++/102163] [10/11/12 Regression] std::variant rejects valid constant expression Date: Tue, 14 Sep 2021 15:23:26 +0000 [thread overview] Message-ID: <bug-102163-4-ItqniIBPlh@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102163-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102163 --- Comment #4 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:de07cff96abd43f6f65dcf333958899c2ec42598 commit r12-3527-gde07cff96abd43f6f65dcf333958899c2ec42598 Author: Patrick Palka <ppalka@redhat.com> Date: Tue Sep 14 11:22:12 2021 -0400 c++: empty union member activation during constexpr [PR102163] Here, the union's constructor is defined to activate its empty data member _M_rest, but during constexpr evaluation of this constructor the subobject constructor call O::O(&_M_rest, 42) doesn't produce a side effect that actually activates the member, so the union still appears uninitialized after its constructor has run. This patch fixes this by using a dummy MODIFY_EXPR in this situation, whose evaluation ensures the member gets activated. PR c++/102163 gcc/cp/ChangeLog: * constexpr.c (cxx_eval_call_expression): After evaluating a subobject constructor call for an empty union member, produce a side effect that makes sure the member gets activated. gcc/testsuite/ChangeLog: * g++.dg/cpp0x/constexpr-empty17.C: New test.
next prev parent reply other threads:[~2021-09-14 15:23 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-01 16:57 [Bug c++/102163] New: " hewillk at gmail dot com 2021-09-01 20:55 ` [Bug c++/102163] [10/11/12 Regression] " ppalka at gcc dot gnu.org 2021-09-01 21:08 ` pinskia at gcc dot gnu.org 2021-09-01 21:09 ` pinskia at gcc dot gnu.org 2021-09-14 15:23 ` cvs-commit at gcc dot gnu.org [this message] 2021-10-06 14:15 ` cvs-commit at gcc dot gnu.org 2021-10-06 14:17 ` [Bug c++/102163] [10 " ppalka at gcc dot gnu.org 2022-06-28 10:46 ` jakub at gcc dot gnu.org 2023-07-07 9:46 ` rguenth 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-102163-4-ItqniIBPlh@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: linkBe 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).