This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/14179] [3.3/3.4/4.0 Regression] out of memory
- From: "mark at codesourcery dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 15 Sep 2004 16:29:59 -0000
- Subject: [Bug c++/14179] [3.3/3.4/4.0 Regression] out of memory
- References: <20040217171044.14179.debora.j.estey@lmco.com>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From mark at codesourcery dot com 2004-09-15 16:29 -------
Subject: Re: [3.3/3.4/4.0 Regression] out of memory
giovannibajo at libero dot it wrote:
>------- Additional Comments From giovannibajo at libero dot it 2004-09-15 14:26 -------
>Mark, one question: are you suggesting the special structure for the
>constructor only before reshape_init or also after it? Because we need to build
>a CONSTRUCTOR sooner or later for the gimplifier.
>
>
Both. After reshape_init is even more critical because that memory
cannot be collected.
>Anyway, would such a change acceptable for Stage 3, being a bugfix towards
>better memory allocation (and fixing this regression)?
>
Perhaps, but it seems unlikely. I've thought about it, but I'm scared
of how much impact there would be through the compiler. There are some
smaller things that we could do more locally, though, like reusing the
TREE_LISTs from before reshape_init after reshape_init. Also, I suspect
that Nathan's integer-sharing work has already reduced this problem
somewhat; part of the problem was that we made multiple copies of every
INTEGER_CST frpm zero up to the upper bound of the array. Now, we
should have only one at least.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14179