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++/98994] [11 Regression] Empty type with [[no_unique_address]] in union with constructor is not a constant expression since r11-6918
Date: Tue, 09 Feb 2021 01:52:34 +0000	[thread overview]
Message-ID: <bug-98994-4-QfXydiakVZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98994-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jason Merrill <jason@gcc.gnu.org>:

https://gcc.gnu.org/g:a8dd2b3e96590ceccead63d28fc91c956a5f1a73

commit r11-7141-ga8dd2b3e96590ceccead63d28fc91c956a5f1a73
Author: Jason Merrill <jason@redhat.com>
Date:   Mon Feb 8 15:56:11 2021 -0500

    c++: constexpr, union, and no_unique_address [PR98994]

    My second patch for 97566 omits nested CONSTRUCTORs for empty fields, but
we
    do want them for empty union members.

    gcc/cp/ChangeLog:

            PR c++/98994
            PR c++/97566
            * constexpr.c (cxx_eval_store_expression): Only skip empty fields
in
            RECORD_TYPE.

    gcc/testsuite/ChangeLog:

            PR c++/98994
            * g++.dg/cpp2a/no_unique_address12.C: New test.

  parent reply	other threads:[~2021-02-09  1:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-08  0:10 [Bug c++/98994] New: Empty type with [[no_unique_address]] in union with constructor is not a constant expression david at doublewise dot net
2021-02-08  9:35 ` [Bug c++/98994] [11 Regression] " rguenth at gcc dot gnu.org
2021-02-08  9:40 ` [Bug c++/98994] [11 Regression] Empty type with [[no_unique_address]] in union with constructor is not a constant expression since r11-6918 jakub at gcc dot gnu.org
2021-02-08 20:41 ` jason at gcc dot gnu.org
2021-02-09  1:52 ` cvs-commit at gcc dot gnu.org [this message]
2021-02-09 14:35 ` jason 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-98994-4-QfXydiakVZ@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).