public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "trippels at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/59659] large zero-initialized std::array compile time excessive
Date: Thu, 09 Jan 2014 17:24:00 -0000	[thread overview]
Message-ID: <bug-59659-4-oUFAwVJL0F@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59659-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59659

--- Comment #7 from Markus Trippelsdorf <trippels at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #6)
> For the #c0 testcase, I think reduced testcase is:
> struct S { S (); S (int); ~S (); int i; };
> struct A { S s[1000000]; };
> 
> void
> foo ()
> {
>   A a = {{}};
> }
> and in that case we don't go through build_vec_init, but
> check_init_r/process_init_constructor etc.

Using (one hundred thousand) "struct A { S s[100000]; };" crashes gcc-4.7, 4.8
and trunk.


  parent reply	other threads:[~2014-01-09 17:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-02 15:25 [Bug c++/59659] New: large zero-initialized std::array of std::atomic " devaneymark at gmail dot com
2014-01-02 16:04 ` [Bug c++/59659] " Casey at Carter dot net
2014-01-07 11:48 ` [Bug c++/59659] large zero-initialized std::array " rguenth at gcc dot gnu.org
2014-01-09 16:18 ` jakub at gcc dot gnu.org
2014-01-09 16:25 ` jakub at gcc dot gnu.org
2014-01-09 16:59 ` trippels at gcc dot gnu.org
2014-01-09 17:03 ` jakub at gcc dot gnu.org
2014-01-09 17:24 ` trippels at gcc dot gnu.org [this message]
2014-01-10 17:16 ` jason at gcc dot gnu.org
2014-01-24 16:48 ` jason at gcc dot gnu.org
2014-01-24 17:09 ` jason 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-59659-4-oUFAwVJL0F@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).