public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "giovannibajo at libero dot it" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/12245] [3.4/4.0/4.1 regression] Uses lots of memory when compiling large initialized arrays
Date: Mon, 12 Sep 2005 10:10:00 -0000 [thread overview]
Message-ID: <20050912100904.29740.qmail@sourceware.org> (raw)
In-Reply-To: <20030911065615.12245.gccBug.9.OkianWarrior@SpamGourmet.com>
------- Additional Comments From giovannibajo at libero dot it 2005-09-12 10:08 -------
The problem is that the gimplifier always want the index field of the
constructor element to be filled. If you fix that in the obvious way (so
that "no index" means "previous index + 1"), it should be quite easy to fix,
for C++. In C, I have no clue how this interacts with designated initializers
though.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12245
next prev parent reply other threads:[~2005-09-12 10:10 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-11 14:50 [Bug c/12245] New: Crashes " gccBug dot 9 dot OkianWarrior at SpamGourmet dot com
2003-09-11 15:53 ` [Bug c/12245] " pinskia at gcc dot gnu dot org
2003-09-11 19:26 ` barrabas at barrabas dot mv dot com
2003-09-11 19:28 ` barrabas at barrabas dot mv dot com
2003-09-17 5:14 ` pinskia at gcc dot gnu dot org
2003-09-17 5:18 ` barrabas at barrabas dot mv dot com
2003-09-17 5:25 ` pinskia at gcc dot gnu dot org
2003-10-01 3:33 ` pinskia at gcc dot gnu dot org
2003-10-01 3:35 ` pinskia at gcc dot gnu dot org
2003-10-05 6:32 ` pinskia at gcc dot gnu dot org
2003-11-22 20:39 ` pinskia at gcc dot gnu dot org
2004-01-19 12:57 ` pinskia at gcc dot gnu dot org
2004-05-26 22:38 ` pinskia at gcc dot gnu dot org
2004-09-12 15:36 ` falk at debian dot org
2004-12-02 15:43 ` pinskia at gcc dot gnu dot org
2004-12-02 15:53 ` [Bug c/12245] [3.4.3/4.0.0 regression] Uses lots of memory " ian at wasabisystems dot com
2004-12-02 15:59 ` [Bug c/12245] [3.3/3.4/4.0 " pinskia at gcc dot gnu dot org
2004-12-02 16:10 ` pinskia at gcc dot gnu dot org
2005-01-06 1:22 ` rth at gcc dot gnu dot org
2005-07-22 18:45 ` [Bug c/12245] [3.4/4.0/4.1 " pinskia at gcc dot gnu dot org
2005-07-25 1:30 ` pinskia at gcc dot gnu dot org
2005-07-25 1:34 ` pinskia at gcc dot gnu dot org
2005-09-12 8:55 ` rguenth at gcc dot gnu dot org
2005-09-12 10:03 ` rguenth at gcc dot gnu dot org
2005-09-12 10:10 ` giovannibajo at libero dot it [this message]
[not found] <bug-12245-6931@http.gcc.gnu.org/bugzilla/>
2005-10-03 17:54 ` rguenth at gcc dot gnu dot org
2005-10-11 19:24 ` rth at gcc dot gnu dot org
2005-10-11 19:30 ` ian at airs 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=20050912100904.29740.qmail@sourceware.org \
--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).