public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/108417] [ICE] Crash on aggregate initialization of base class
Date: Mon, 16 Jan 2023 16:19:46 +0000	[thread overview]
Message-ID: <bug-108417-4-09mANRRxUt@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108417-4@http.gcc.gnu.org/bugzilla/>

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           See Also|                            |https://gcc.gnu.org/bugzill
                   |                            |a/show_bug.cgi?id=90254

--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Note in c++17 the copy is required to be elision away. And the frontend is
doing that but messing up. The problems are all related really. The question
comes should they be elision away or not and that is what the c++ defect report
is about and the same way the abi issue is about.

  parent reply	other threads:[~2023-01-16 16:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-16 13:25 [Bug c++/108417] New: " m.cencora at gmail dot com
2023-01-16 14:04 ` [Bug c++/108417] " m.cencora at gmail dot com
2023-01-16 14:17 ` rguenth at gcc dot gnu.org
2023-01-16 15:19 ` pinskia at gcc dot gnu.org
2023-01-16 15:37 ` m.cencora at gmail dot com
2023-01-16 16:19 ` pinskia at gcc dot gnu.org [this message]
2023-01-17  2:24 ` pinskia at gcc dot gnu.org
2023-01-17 12:57 ` m.cencora at gmail dot com

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-108417-4-09mANRRxUt@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).