public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Marek Polacek <polacek@redhat.com>
To: Stephan Bergmann <sberg.fun@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
	Jason Merrill <jason@redhat.com>,
	Jakub Jelinek <jakub@redhat.com>
Subject: Re: [PATCH v2] c++: direct-init of an array of class type [PR59465]
Date: Mon, 25 Mar 2024 15:58:44 -0400	[thread overview]
Message-ID: <ZgHXdDDHaVB52WXv@redhat.com> (raw)
In-Reply-To: <00a94aed-9f4c-4d57-941e-39d24e38fd68@gmail.com>

On Mon, Mar 25, 2024 at 01:39:39PM +0100, Stephan Bergmann wrote:
> On 3/25/24 13:07, Jakub Jelinek wrote:
> > On Mon, Mar 25, 2024 at 12:36:46PM +0100, Stephan Bergmann wrote:
> > > This started to break
> > > 
> > > > $ cat test.cc
> > > > struct S1 { S1(); };
> > > > struct S2 {
> > > >      S2() {}
> > > >      S1 a[1] {};
> > > > };
> > > 
> > > > $ g++ -fsyntax-only test.cc
> > > > test.cc: In constructor ‘S2::S2()’:
> > > > test.cc:3:10: error: invalid initializer for array member ‘S1 S2::a [1]’
> > > >      3 |     S2() {}
> > > >        |          ^
> > 
> > https://gcc.gnu.org/PR114439 ?
> 
> yes, sorry, missed that already-existing bugracker issue

I have a patch now, sorry about the breakage.  I'm surprised we had no test
covering this :(.

Marek


      reply	other threads:[~2024-03-25 19:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-02  0:58 [PATCH] " Marek Polacek
2024-03-19 19:51 ` Marek Polacek
2024-03-21  1:21 ` Jason Merrill
2024-03-21 20:48   ` [PATCH v2] " Marek Polacek
2024-03-21 21:28     ` Jason Merrill
2024-03-25 11:36       ` Stephan Bergmann
2024-03-25 12:07         ` Jakub Jelinek
2024-03-25 12:39           ` Stephan Bergmann
2024-03-25 19:58             ` Marek Polacek [this message]

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=ZgHXdDDHaVB52WXv@redhat.com \
    --to=polacek@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=jason@redhat.com \
    --cc=sberg.fun@gmail.com \
    /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).