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++/100111] [10 Regression] `-fno-elide-constructors` with `constexpr` ctors causes ICE in GCC 10.3
Date: Wed, 13 Apr 2022 14:18:22 +0000	[thread overview]
Message-ID: <bug-100111-4-3kifgUKI8H@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100111-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #11 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:ec03862f809e544a9b7d28067e51597dc92a0244

commit r12-8144-gec03862f809e544a9b7d28067e51597dc92a0244
Author: Jason Merrill <jason@redhat.com>
Date:   Tue Apr 12 17:46:59 2022 -0400

    c++: empty base constexpr -fno-elide-ctors [PR105245]

    The patch for 100111 extended our handling of empty base elision to the
case
    where the derived class has no other fields, but we still need to make sure
    that there's some initializer for the derived object.

            PR c++/105245
            PR c++/100111

    gcc/cp/ChangeLog:

            * constexpr.cc (cxx_eval_store_expression): Build a CONSTRUCTOR
            as needed in empty base handling.

    gcc/testsuite/ChangeLog:

            * g++.dg/cpp1y/constexpr-empty2.C: Add -fno-elide-constructors.

  parent reply	other threads:[~2022-04-13 14:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-16  5:37 [Bug c++/100111] New: `-fno-elide-constructors` " lh_mouse at 126 dot com
2021-04-16  7:36 ` [Bug c++/100111] [10/11 Regression] `-fno-elide-constructors` with `constexpr` ctors " rguenth at gcc dot gnu.org
2021-04-16  8:14 ` jakub at gcc dot gnu.org
2021-04-16  9:04 ` jakub at gcc dot gnu.org
2021-04-16 10:16 ` jakub at gcc dot gnu.org
2021-04-16 11:11 ` lh_mouse at 126 dot com
2021-04-16 14:01 ` lh_mouse at 126 dot com
2021-04-16 14:10 ` jason at gcc dot gnu.org
2021-04-16 15:44 ` cvs-commit at gcc dot gnu.org
2021-04-17  3:33 ` [Bug c++/100111] [10 " jason at gcc dot gnu.org
2021-04-20  9:46 ` cvs-commit at gcc dot gnu.org
2021-04-20  9:53 ` jakub at gcc dot gnu.org
2022-04-13 14:18 ` cvs-commit at gcc dot gnu.org [this message]
2022-05-06 20:30 ` cvs-commit at gcc dot gnu.org
2022-05-12 20:13 ` cvs-commit at gcc dot gnu.org
2022-05-12 21:15 ` cvs-commit 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-100111-4-3kifgUKI8H@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).