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++/108559] [13 Regression] A new crash with using a simple class, inheritance and a function
Date: Wed, 01 Feb 2023 00:11:25 +0000	[thread overview]
Message-ID: <bug-108559-4-o9mVmvtWhR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108559-4@http.gcc.gnu.org/bugzilla/>

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

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

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

commit r13-5611-gb533084d756a2696a3eb6521810e0a0b2182a8e8
Author: Jason Merrill <jason@redhat.com>
Date:   Mon Jan 30 18:18:54 2023 -0500

    c++: aggregate base and TARGET_EXPR_ELIDING_P [PR108559]

    We also need to split up a CONSTRUCTOR in cp_genericize_init if we need to
    add extra copy constructor calls to deal with CWG2403.

            PR c++/108559

    gcc/cp/ChangeLog:

            * cp-gimplify.cc (any_non_eliding_target_exprs): New.
            (cp_genericize_init): Check it.

    gcc/testsuite/ChangeLog:

            * g++.dg/cpp1z/aggr-base13.C: New test.

  parent reply	other threads:[~2023-02-01  0:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-26 12:22 [Bug c++/108559] New: " zakkariusr at gmail dot com
2023-01-26 12:25 ` [Bug c++/108559] [13 Regression] " redi at gcc dot gnu.org
2023-01-26 12:51 ` rguenth at gcc dot gnu.org
2023-01-26 16:31 ` pinskia at gcc dot gnu.org
2023-01-30 22:46 ` jason at gcc dot gnu.org
2023-01-30 23:16 ` jason at gcc dot gnu.org
2023-02-01  0:11 ` cvs-commit at gcc dot gnu.org [this message]
2023-02-01  0:15 ` jason at gcc dot gnu.org
2023-02-01 15:11 ` mpolacek 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-108559-4-o9mVmvtWhR@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).