This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug tree-optimization/36291] GCC is slow and memory-hungry building sipQtGuipart.cpp
- From: "hubicka at ucw dot cz" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 26 May 2008 14:20:46 -0000
- Subject: [Bug tree-optimization/36291] GCC is slow and memory-hungry building sipQtGuipart.cpp
- References: <bug-36291-10053@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #8 from hubicka at ucw dot cz 2008-05-26 14:20 -------
Subject: Re: GCC is slow and memory-hungry building sipQtGuipart.cpp
> As noted in comment #1 variable annotations are a major problem (they are
> duplicated for global variables, for each function the variable is referenced
> from).
>
> It happens that sharing variable annotations for globals between functions
> reduces peak memory usage by 1GB. So that's were I'm currently looking at.
The problem of var annotations is that they contain a lot of local stuff
+ little of stuff that is specific per function (that is aliasing info,
for instance).
Breaking out the local stuff and allocating the global stuff only where
needed is way I wanted to go for a while, but we never got actually into
agreement how to get there.
Honza
>
>
> --
>
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36291
>
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug, or are watching someone who is.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36291