On Thu, 21 Apr 2011, Laurynas Biveinis wrote:
:( Why don't you get yourself a compile farm account?
http://gcc.gnu.org/wiki/CompileFarm
Thanks Laurynas, I am absolutely thrilled to see such a variety of
hardware! I'll try applying, but I'm not sure I'm eligible, my
contributions to OSS are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/20/11 17:35, Dimitrios Apostolou wrote:
>
> Plus a whole page which is preallocated by the obstack, if I understand
> correctly. As a result, for each word in the text file we consume 4KB,
> which are never freed.
Plausible. Though I always th
Dimitrios -
The patch is OK with a ChangeLog entry. Also a patch to fix the same
in gengtype.c:matching_file_name_substitute is pre-approved (but it
looks like Jeff will beat you to this :)
> P.S. I was trying to test gcc on a rare arch (sparc-unknown-linux-gnu) but
> unfortunately the sparcstati
On Wed, 20 Apr 2011, Jeff Law wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/20/11 15:08, Dimitrios Apostolou wrote:
Hello list,
while trying to build gcc-4.6.0 on my sparcstation, I got gengtype OOM
killed. That's when I noticed that its RAM usage peaks at 150MB, which
is a bit ex
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/20/11 15:08, Dimitrios Apostolou wrote:
> Hello list,
>
> while trying to build gcc-4.6.0 on my sparcstation, I got gengtype OOM
> killed. That's when I noticed that its RAM usage peaks at 150MB, which
> is a bit excessive for parsing a ~500K te
Hello list,
while trying to build gcc-4.6.0 on my sparcstation, I got gengtype OOM
killed. That's when I noticed that its RAM usage peaks at 150MB, which is
a bit excessive for parsing a ~500K text file.
The attached patch fixes the leak and gengtype now uses a peak of 4MB
heap. Hopefully I
