public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "rob1weld at aol dot com" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug java/38717] gcc 4.4.0 20090102 - jc1: out of memory allocating ... (with 1 G of RAM)
Date: Sat, 17 Jan 2009 14:41:00 -0000	[thread overview]
Message-ID: <20090117144115.20323.qmail@sourceware.org> (raw)
In-Reply-To: <bug-38717-13830@http.gcc.gnu.org/bugzilla/>



------- Comment #7 from rob1weld at aol dot com  2009-01-17 14:41 -------
Created an attachment (id=17127)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=17127&action=view)
Screenshot of build shows libgcj_tools building (after reboot)

Before reboot:

# gmake
...
gmake[3]: Entering directory
`/usr/share/src/gcc_build/i386-pc-solaris2.11/libjava'
if /bin/sh ./libtool --tag=GCJ --mode=compile /usr/share/src/gcc_build/gcc/gcj
-B/usr/share/src/gcc_build/i386-pc-solaris2.11/libjava/
-B/usr/share/src/gcc_build/gcc/ -ffloat-store -fomit-frame-pointer -Usun
-fclasspath= -fbootclasspath=../../../gcc_trunk/libjava/classpath/lib
--encoding=UTF-8 -Wno-deprecated -fbootstrap-classes -findirect-dispatch
-fno-indirect-classes 
-fsource-filename=/usr/share/src/gcc_build/i386-pc-solaris2.11/libjava/classpath/tools/all-classes.lst
-g -O2 -MT classpath/tools/libgcj_tools_la-tools.lo -MD -MP -MF
"classpath/tools/.deps/libgcj_tools_la-tools.Tpo" -c -o
classpath/tools/libgcj_tools_la-tools.lo `test -f 'classpath/tools/tools.zip'
|| echo '../../../gcc_trunk/libjava/'`classpath/tools/tools.zip; \
        then mv -f "classpath/tools/.deps/libgcj_tools_la-tools.Tpo"
"classpath/tools/.deps/libgcj_tools_la-tools.Plo"; else rm -f
"classpath/tools/.deps/libgcj_tools_la-tools.Tpo"; exit 1; fi
libtool: compile:  /usr/share/src/gcc_build/gcc/gcj
-B/usr/share/src/gcc_build/i386-pc-solaris2.11/libjava/
-B/usr/share/src/gcc_build/gcc/ -ffloat-store -fomit-frame-pointer -Usun
-fclasspath= -fbootclasspath=../../../gcc_trunk/libjava/classpath/lib
--encoding=UTF-8 -Wno-deprecated -fbootstrap-classes -findirect-dispatch
-fno-indirect-classes
-fsource-filename=/usr/share/src/gcc_build/i386-pc-solaris2.11/libjava/classpath/tools/all-classes.lst
-g -O2 -MT classpath/tools/libgcj_tools_la-tools.lo -MD -MP -MF
classpath/tools/.deps/libgcj_tools_la-tools.Tpo -c classpath/tools/tools.zip 
-fPIC -o classpath/tools/.libs/libgcj_tools_la-tools.o

jc1: out of memory allocating 4072 bytes after a total of 688709632 bytes
gmake[3]: *** [classpath/tools/libgcj_tools_la-tools.lo] Error 1
gmake[3]: Leaving directory
`/usr/share/src/gcc_build/i386-pc-solaris2.11/libjava'
gmake[2]: *** [all-recursive] Error 1
gmake[2]: Leaving directory
`/usr/share/src/gcc_build/i386-pc-solaris2.11/libjava'
gmake[1]: *** [all-target-libjava] Error 2
gmake[1]: Leaving directory `/usr/share/src/gcc_build'


After reboot:

# gmake
...
libtool: link:  /usr/share/src/gcc_build/./gcc/xgcc -shared-libgcc
-B/usr/share/src/gcc_build/./gcc -nostdinc++
-L/usr/share/src/gcc_build/i386-pc-solaris2.11/libstdc++-v3/src
-L/usr/share/src/gcc_build/i386-pc-solaris2.11/libstdc++-v3/src/.libs
-B/usr/local/i386-pc-solaris2.11/bin/ -B/usr/local/i386-pc-solaris2.11/lib/
-isystem /usr/local/i386-pc-solaris2.11/include -isystem
/usr/local/i386-pc-solaris2.11/sys-include -shared -nostdlib /usr/lib/crti.o
/usr/lib/values-Xa.o /usr/share/src/gcc_build/./gcc/crtbegin.o 
classpath/tools/.libs/libgcj_tools_la-tools.o  
-L/usr/share/src/gcc_build/i386-pc-solaris2.11/libstdc++-v3/src
-L/usr/share/src/gcc_build/i386-pc-solaris2.11/libstdc++-v3/src/.libs
-L/usr/share/src/gcc_build/i386-pc-solaris2.11/libjava
-L/usr/share/src/gcc_build/./gcc -L/usr/local/i386-pc-solaris2.11/bin
-L/usr/local/i386-pc-solaris2.11/lib -lgcc_s
/usr/share/src/gcc_build/./gcc/crtend.o /usr/lib/crtn.o 
-Wl,--version-script=../../../gcc_trunk/libjava/libgcj.ver
-Wl,-Bsymbolic-functions   -Wl,-soname -Wl,libgcj-tools.so.10 -o
.libs/libgcj-tools.so.10.0.0
libtool: link: (cd ".libs" && rm -f "libgcj-tools.so.10" && ln -s
"libgcj-tools.so.10.0.0" "libgcj-tools.so.10")
libtool: link: (cd ".libs" && rm -f "libgcj-tools.so" && ln -s
"libgcj-tools.so.10.0.0" "libgcj-tools.so")
libtool: link: ( cd ".libs" && rm -f "libgcj-tools.la" && ln -s
"../libgcj-tools.la" "libgcj-tools.la" )
...


I was at a point were the size of gcc's build was very near all the memory
that I had available and I needed to reboot my OS to ensure I had every
last byte available. With the reboot I was just barely able to compile
the second 'libgcj_tools' using the maximum available under VirtualBox.


-- 


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


  parent reply	other threads:[~2009-01-17 14:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-03 17:13 [Bug java/38717] New: " rob1weld at aol dot com
2009-01-03 17:16 ` [Bug java/38717] " pinskia at gcc dot gnu dot org
2009-01-06  3:10 ` rob1weld at aol dot com
2009-01-12  0:09 ` rob1weld at aol dot com
2009-01-12 12:47 ` rob1weld at aol dot com
2009-01-14 17:24 ` rob1weld at aol dot com
2009-01-17 14:32 ` rob1weld at aol dot com
2009-01-17 14:41 ` rob1weld at aol dot com [this message]
2009-01-22 15:12 ` rob1weld at aol dot com
2009-01-22 16:03 ` rob1weld at aol dot com

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=20090117144115.20323.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=java-prs@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).