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++/106369] [12 Regression] ICE in output_constructor_regular_field, at varasm.cc:5515 since r12-2975-g32c3a75390623a
Date: Fri, 12 Aug 2022 08:11:16 +0000	[thread overview]
Message-ID: <bug-106369-4-i5zgk0hDS3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106369-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #14 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-12 branch has been updated by Richard Biener
<rguenth@gcc.gnu.org>:

https://gcc.gnu.org/g:6b7d570a5001bb79e34c0d1626a8c7f55386dac7

commit r12-8684-g6b7d570a5001bb79e34c0d1626a8c7f55386dac7
Author: Jason Merrill <jason@redhat.com>
Date:   Tue Jul 26 11:02:21 2022 -0400

    c++: constexpr, empty base after non-empty [PR106369]

    Here the CONSTRUCTOR we were providing for D{} had an entry for the B base
    subobject at offset 0 following the entry for the C base, causing
    output_constructor_regular_field to ICE due to going backwards.  It might
be
    nice for that function to be more tolerant of empty fields, but it also
    seems reasonable for the front end to prune the useless entry.

            PR c++/106369

    gcc/cp/ChangeLog:

            * constexpr.cc (reduced_constant_expression_p): Return false
            if a CONSTRUCTOR initializes an empty field.

    gcc/testsuite/ChangeLog:

            * g++.dg/cpp1z/constexpr-lambda27.C: New test.

    (cherry picked from commit 9efe4e153d994974afcbba09c3c683f5f4a19c63)

  parent reply	other threads:[~2022-08-12  8:11 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-20 10:26 [Bug c++/106369] New: ICE in output_constructor_regular_field, at varasm.cc:5515 h2+bugs at fsfe dot org
2022-07-20 12:09 ` [Bug c++/106369] " rguenth at gcc dot gnu.org
2022-07-20 15:33 ` mpolacek at gcc dot gnu.org
2022-07-20 15:35 ` [Bug c++/106369] [12/13 Regression] " pinskia at gcc dot gnu.org
2022-07-20 15:47 ` pinskia at gcc dot gnu.org
2022-07-20 21:07 ` pinskia at gcc dot gnu.org
2022-07-21 11:11 ` h2+bugs at fsfe dot org
2022-07-21 15:24 ` [Bug c++/106369] [12/13 Regression] ICE in output_constructor_regular_field, at varasm.cc:5515 since r12-2975-g32c3a75390623a pinskia at gcc dot gnu.org
2022-07-25 15:02 ` rguenth at gcc dot gnu.org
2022-07-25 22:49 ` ppalka at gcc dot gnu.org
2022-07-26  6:42 ` rguenther at suse dot de
2022-07-26  9:15 ` jakub at gcc dot gnu.org
2022-07-26  9:19 ` jakub at gcc dot gnu.org
2022-07-26 14:31 ` jason at gcc dot gnu.org
2022-07-31  6:05 ` cvs-commit at gcc dot gnu.org
2022-08-10 13:13 ` [Bug c++/106369] [12 " rguenth at gcc dot gnu.org
2022-08-12  8:11 ` cvs-commit at gcc dot gnu.org [this message]
2022-08-12  8:12 ` 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-106369-4-i5zgk0hDS3@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).