From: Richard Guenther <richard.guenther@gmail.com>
To: Steven Bosscher <stevenb@suse.de>
Cc: "Joseph S. Myers" <joseph@codesourcery.com>,
Ian Lance Taylor <ian@wasabisystems.com>,
mark@codesourcery.com, gcc@gcc.gnu.org
Subject: Re: Compiler uses a lot of memory for large initialized arrays
Date: Thu, 02 Dec 2004 17:12:00 -0000 [thread overview]
Message-ID: <84fc9c000412020912298ed15c@mail.gmail.com> (raw)
In-Reply-To: <425929.1102007117190.SLOX.WebMail.wwwrun@extimap.suse.de>
On Thu, 2 Dec 2004 18:05:17 +0100 (CET), Steven Bosscher
<stevenb@suse.de> wrote:
> On Dec 02, 2004 05:34 PM, Joseph S. Myers <joseph@codesourcery.com> wrote:
>
> > On Thu, 2 Dec 2004, Ian Lance Taylor wrote:
> >
> > > This test case works fine with 2.95.3. Looking into the patches I
> > > came across this note from you from four years ago:
> > > http://gcc.gnu.org/ml/gcc-patches/2000-10/msg00937.html
> >
> > And hopefully you came across the November part of the thread as well: C99
> > designated initializers allow
> >
> > int i[10000000] = { 0, 1, 2, 3, 4, 5, /* ... */
> > 9999998, 9999999, [0] = -1 };
> >
> > which stops optimizing in the simplest way by writing out initializers to
> > the assembler output before the whole initializer has been parsed.
>
> Ouch.
>
> Do we disable this if -std!=c99?
Or can't we seek in the asm output and overwrite previously written values?
Might be slow, though.
Richard.
next prev parent reply other threads:[~2004-12-02 17:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-02 16:08 Ian Lance Taylor
2004-12-02 16:34 ` Joseph S. Myers
2004-12-02 17:03 ` Ian Lance Taylor
2004-12-02 17:05 ` Steven Bosscher
2004-12-02 17:12 ` Richard Guenther [this message]
2004-12-02 17:17 ` Nathan Sidwell
2004-12-02 17:29 ` Peter Barada
2004-12-02 17:39 ` Mark Mitchell
2004-12-02 17:42 ` Ian Lance Taylor
2004-12-02 17:49 ` Dave Korn
2004-12-02 17:36 ` Andreas Schwab
2004-12-02 18:18 ` Joe Buck
2004-12-02 18:23 ` Mark Mitchell
2004-12-02 17:31 ` Mark Mitchell
2004-12-02 17:33 ` Giovanni Bajo
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=84fc9c000412020912298ed15c@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=ian@wasabisystems.com \
--cc=joseph@codesourcery.com \
--cc=mark@codesourcery.com \
--cc=stevenb@suse.de \
/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).