[Bug tree-optimization/32199] New: jc1: out of memory allocating 4072 bytes after a total of 805021000 bytes

[Bug tree-optimization/32199] New: jc1: out of memory allocating 4072 bytes after a total of 805021000 bytes

[danglin at gcc dot gnu dot org]

libjava fails to build:

/mnt/gnu/gcc/objdir/gcc/gcj
-B/mnt/gnu/gcc/objdir/hppa2.0w-hp-hpux11.11/libjava/
 -B/mnt/gnu/gcc/objdir/gcc/ -fclasspath=
-fbootclasspath=/mnt/gnu/gcc/objdir/hpp
a2.0w-hp-hpux11.11/libjava/classpath/lib --encoding=UTF-8 -Wno-deprecated
-fboot
strap-classes -g -O2 -fjni -findirect-dispatch -fno-indirect-classes -c
@org-omg
.list -fPIC -o .libs/org-omg.o

jc1: out of memory allocating 4072 bytes after a total of 805021000 bytes
make[3]: *** [org-omg.lo] Error 1
make[3]: *** Waiting for unfinished jobs....

This seems similar to a previous tree optimization bug.


-- 
           Summary: jc1: out of memory allocating 4072 bytes after a total
                    of 805021000 bytes
           Product: gcc
           Version: 4.2.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: danglin at gcc dot gnu dot org
 GCC build triplet: hppa2.0w-hp-hpux11.11
  GCC host triplet: hppa2.0w-hp-hpux11.11
GCC target triplet: hppa2.0w-hp-hpux11.11


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32199

[Bug tree-optimization/32199] jc1: out of memory allocating 4072 bytes after a total of 805021000 bytes

[danglin at gcc dot gnu dot org]

------- Comment #1 from danglin at gcc dot gnu dot org  2007-06-05 23:43 -------
This was introduced in revision 125227.


-- 

danglin at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dberlin at gcc dot gnu dot
                   |                            |org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32199

[Bug tree-optimization/32199] jc1: out of memory allocating 4072 bytes after a total of 805021000 bytes

[dberlin at gcc dot gnu dot org]

------- Comment #2 from dberlin at gcc dot gnu dot org  2007-06-05 23:49 -------
And the memory usage before that revision was what?


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32199

[Bug tree-optimization/32199] jc1: out of memory allocating 4072 bytes after a total of 805021000 bytes

[ro at gcc dot gnu dot org]

------- Comment #3 from ro at gcc dot gnu dot org  2007-06-20 09:44 -------
I observe the same problem (also affecting gnu-xml.lo) on
alpha-dec-osf{4.0f,5.1b}.
VM consumption for org-omg.lo is at 1.5 GB now, a machine with 768 MB physical 
memory crawls along for hours compiling the file.  I had to double swap space
from 2 GB to 4 GB to be able to compile at all, while there was on such problem
in gcc 4.2.0 as of 20070506.


-- 

ro at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ro at gcc dot gnu dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32199

[Bug tree-optimization/32199] jc1: out of memory allocating 4072 bytes after a total of 805021000 bytes

[danglin at gcc dot gnu dot org]

------- Comment #4 from danglin at gcc dot gnu dot org  2007-07-12 18:50 -------
I tried increasing the kernel maxdsiz limits to 2 GB.  However, we
still die after allocating roughly the same number of bytes.

In 32-bit PA runtime, malloc allocates memory using brk and sbrk
from the data segment.  The size of the data segment is 1 GB.
I believe we have reached the 1 GB limit for at least two compilations
in libjava.

The ulimit command (bash, ksh and sh) doesn't correctly indicate
the 1 GB limit of the data segment.  I suspect getrlimit also doesn't
reflect the runtime limit.  Possibly, reducing maxdsiz might trigger
more garbage collection.

At last check, libjava still builds on the trunk.  So, 4.2.1 is using
more memory.  Libjava builds under linux.  The linux runtime uses a
flat memory model and thus has more space available for data.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32199

[Bug tree-optimization/32199] jc1: out of memory allocating 4072 bytes after a total of 805021000 bytes

[dberlin at gcc dot gnu dot org]

------- Comment #5 from dberlin at gcc dot gnu dot org  2007-07-12 19:15 -------
I have a few upcoming patches that should seriously reduce memory usage of
points-to.
If they work on mainline, i will backport them to 4.2
Please be patient, sorry for this :)


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32199

[Bug tree-optimization/32199] jc1: out of memory allocating 4072 bytes after a total of 805021000 bytes

[dave at hiauly1 dot hia dot nrc dot ca]

------- Comment #6 from dave at hiauly1 dot hia dot nrc dot ca  2007-07-12 19:21 -------
Subject: Re:  jc1: out of memory allocating 4072 bytes after a total of
805021000 bytes

> I have a few upcoming patches that should seriously reduce memory usage of
> points-to.

Sounds good.

Dave


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32199

[Bug tree-optimization/32199] jc1: out of memory allocating 4072 bytes after a total of 805021000 bytes

[mmitchel at gcc dot gnu dot org]

------- Comment #7 from mmitchel at gcc dot gnu dot org  2007-07-16 02:25 -------
Because this is a Java issue, I'm not too concerned about this -- but because
it breaks the build, I'm more concerned than I would be if it was "just" a bug
in using Java.  So, I've marked this P2.


-- 

mmitchel at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P3                          |P2


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32199

[Bug tree-optimization/32199] jc1: out of memory allocating 4072 bytes after a total of 805021000 bytes

[dberlin at dberlin dot org]

------- Comment #8 from dberlin at gcc dot gnu dot org  2007-07-16 13:41 -------
Subject: Re:  jc1: out of memory allocating 4072 bytes after a total of
805021000 bytes

Hi guys, can you check whether the 32723 fix that was just checked in
fixes this?
I believe it might (it should make 4.2 branch roughly as memory
efficient as mainline here)


On 16 Jul 2007 02:25:33 -0000, mmitchel at gcc dot gnu dot org
<gcc-bugzilla@gcc.gnu.org> wrote:
>
>
> ------- Comment #7 from mmitchel at gcc dot gnu dot org  2007-07-16 02:25 -------
> Because this is a Java issue, I'm not too concerned about this -- but because
> it breaks the build, I'm more concerned than I would be if it was "just" a bug
> in using Java.  So, I've marked this P2.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32199

[Bug tree-optimization/32199] jc1: out of memory allocating 4072 bytes after a total of 805021000 bytes

[dave at hiauly1 dot hia dot nrc dot ca]

------- Comment #9 from dave at hiauly1 dot hia dot nrc dot ca  2007-07-16 16:16 -------
Subject: Re:  jc1: out of memory allocating 4072 bytes after a total of
805021000 bytes

> Hi guys, can you check whether the 32723 fix that was just checked in
> fixes this?

Doesn't seem to be checked in yet.

Dave


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32199

[Bug tree-optimization/32199] jc1: out of memory allocating 4072 bytes after a total of 805021000 bytes

[rguenth at gcc dot gnu dot org]

------- Comment #10 from rguenth at gcc dot gnu dot org  2007-07-16 19:38 -------
The patch requires RM approval.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32199

[Bug tree-optimization/32199] jc1: out of memory allocating 4072 bytes after a total of 805021000 bytes

[dave at hiauly1 dot hia dot nrc dot ca]

------- Comment #11 from dave at hiauly1 dot hia dot nrc dot ca  2007-07-17 01:06 -------
Subject: Re:  jc1: out of memory allocating 4072 bytes after a total of
805021000 bytes

> Hi guys, can you check whether the 32723 fix that was just checked in
> fixes this?

Still same problem with the 32723 fix:

jc1: out of memory allocating 4072 bytes after a total of 804656392 bytes
make[3]: *** [org-omg.lo] Error 1
make[3]: *** Waiting for unfinished jobs....

jc1: out of memory allocating 4072 bytes after a total of 707351816 bytes
make[3]: *** [gnu-xml.lo] Error 1

Dave


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32199

[Bug tree-optimization/32199] jc1: out of memory allocating 4072 bytes after a total of 805021000 bytes

[alex dot d at bugmenot dot com]

------- Comment #12 from alex dot d at bugmenot dot com  2007-09-19 14:38 -------
I've a similar problem when building SDL library (1.2.12), when using -O3
compilation flag. I'll try to attach an .i file that triggers the bug. After
starting the compilation, the memory starts getting consumed seemingly
indefinitely, eating all physical then swap, making system very unresponsive.
When ulimit-ing it to some sane values it crashes with messages like this:

cc1: out of memory allocating 4064 bytes after a total of 57159680 bytes

The command line:

gcc -O3 SDL_x11dyn.i

gcc -v output:

Target: i686-pc-linux-gnu
Configured with: ../configure --prefix=/usr --enable-shared
--enable-languages=c,c++,objc --enable-threads=posix --enable-__cxa_atexit
--disable-multilib --libdir=/usr/lib --libexecdir=/usr/lib --enable-clocale=gnu
--disable-libstdcxx-pch --with-tune=generic
Thread model: posix
gcc version 4.2.1
[..]
GNU C version 4.2.1 (i686-pc-linux-gnu)
        compiled by GNU C version 4.2.1.
GGC heuristics: --param ggc-min-expand=36 --param ggc-min-heapsize=27924


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32199

[Bug tree-optimization/32199] jc1: out of memory allocating 4072 bytes after a total of 805021000 bytes

[alex dot d at bugmenot dot com]

------- Comment #13 from alex dot d at bugmenot dot com  2007-09-19 14:43 -------
Created an attachment (id=14223)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=14223&action=view)
consumes all memory when compiled with -O3


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32199

[Bug tree-optimization/32199] jc1: out of memory allocating 4072 bytes after a total of 805021000 bytes

[merkil at savhon dot org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32199

--- Comment #17 from Antoine Balestrat <merkil at savhon dot org> 2012-03-26 15:56:33 UTC ---
Created attachment 27001
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=27001
gcc -O2 -v memfail.c

[Bug tree-optimization/32199] jc1: out of memory allocating 4072 bytes after a total of 805021000 bytes

[merkil at savhon dot org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32199

--- Comment #16 from Antoine Balestrat <merkil at savhon dot org> 2012-03-26 15:55:07 UTC ---
Created attachment 27000
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=27000
The source that causes excessive memory usage

[Bug tree-optimization/32199] jc1: out of memory allocating 4072 bytes after a total of 805021000 bytes

[merkil at savhon dot org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32199

Antoine Balestrat <merkil at savhon dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |merkil at savhon dot org

--- Comment #15 from Antoine Balestrat <merkil at savhon dot org> 2012-03-26 15:52:46 UTC ---
I'm having the same issue, but with a C program. It fails with gcc as of 4.8.0
20120324, but I can reproduce it with 4.6.3 and 4.5.3.
I'm adding the source and the complete build log as an attachment.

[Bug tree-optimization/32199] jc1: out of memory allocating 4072 bytes after a total of 805021000 bytes

[xiaoyuanbo at yeah dot net]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32199

xiaoyuanbo <xiaoyuanbo at yeah dot net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |xiaoyuanbo at yeah dot net

--- Comment #14 from xiaoyuanbo <xiaoyuanbo at yeah dot net> 2012-02-22 12:59:27 UTC ---
install gcc event