public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "niemayer at isg dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/12245] [4.0/4.1/4.2/4.3 regression] Uses lots of memory when compiling large initialized arrays
Date: Thu, 17 Jan 2008 17:45:00 -0000 [thread overview]
Message-ID: <20080117170208.32549.qmail@sourceware.org> (raw)
In-Reply-To: <bug-12245-6931@http.gcc.gnu.org/bugzilla/>
------- Comment #34 from niemayer at isg dot de 2008-01-17 17:02 -------
Can you suggest any kind of work-around? Any alternative to represent constant
arrays in C/C++?
The problem with leaving this bug open indefinitely is that there are existing
programs (as the Unicode-test-case I mentioned above) which will simply not
compile on any reasonably equipped machine anymore.
I wouldn't mind to change the source code to represent the constant arrays in a
different way, but I have not found a method yet (other than using platform
dependend methods like generating assembler source).
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12245
next prev parent reply other threads:[~2008-01-17 17:02 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-12245-6931@http.gcc.gnu.org/bugzilla/>
2005-10-03 17:54 ` [Bug c/12245] [3.4/4.0/4.1 " 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
2006-12-13 11:37 ` [Bug c/12245] [4.0/4.1/4.2/4.3 " niemayer at isg dot de
2007-05-14 21:26 ` mmitchel at gcc dot gnu dot org
2007-05-15 15:54 ` niemayer at isg dot de
2007-05-15 16:05 ` pluto at agmk dot net
2007-07-20 3:50 ` mmitchel at gcc dot gnu dot org
2007-10-09 19:25 ` mmitchel at gcc dot gnu dot org
2008-01-05 16:02 ` rguenth at gcc dot gnu dot org
2008-01-17 17:00 ` jsm28 at gcc dot gnu dot org
2008-01-17 17:45 ` niemayer at isg dot de [this message]
2008-01-18 8:46 ` ian at airs dot com
2008-02-01 16:53 ` jsm28 at gcc dot gnu dot org
2008-05-19 20:23 ` [Bug c/12245] [4.1/4.2/4.3/4.4 " jsm28 at gcc dot gnu dot org
2008-07-04 22:44 ` [Bug c/12245] [4.2/4.3/4.4 " jsm28 at gcc dot gnu dot org
2009-02-10 10:12 ` rguenth at gcc dot gnu dot org
2009-02-21 12:40 ` hubicka at gcc dot gnu dot org
2009-02-21 12:50 ` rguenther at suse dot de
2009-02-22 11:21 ` hubicka at gcc dot gnu dot org
2009-02-22 19:04 ` rguenther at suse dot de
2009-02-23 13:42 ` hubicka at gcc dot gnu dot org
2009-02-23 16:47 ` hubicka at gcc dot gnu dot org
2009-03-31 16:13 ` [Bug c/12245] [4.3/4.4/4.5 " jsm28 at gcc dot gnu dot org
2009-08-04 12:27 ` rguenth at gcc dot gnu dot org
2010-05-22 18:11 ` [Bug c/12245] [4.3/4.4/4.5/4.6 " rguenth at gcc dot gnu dot 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=20080117170208.32549.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).