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:32:00 -0000 [thread overview] Message-ID: <20090117143236.16339.qmail@sourceware.org> (raw) In-Reply-To: <bug-38717-13830@http.gcc.gnu.org/bugzilla/> ------- Comment #6 from rob1weld at aol dot com 2009-01-17 14:32 ------- Created an attachment (id=17126) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=17126&action=view) Screenshot of build shows libgcj_tools crashing (hogging memory) Here we have a screenshot of gcc building 'libgcj_tools' (the two humps) and crashing on the second one. The next attachment (a reboot was necessary to continue the build) shows that the second hump completes and the build finished shortly thereafter. I configured gcc using: # gcc/xgcc -v Using built-in specs. Target: i386-pc-solaris2.11 Configured with: ../gcc_trunk/configure --enable-languages=ada,c,c++,fortran,java,objc,obj-c++ --enable-shared --disable-static --enable-decimal-float --with-long-double-128 --enable-nls --with-included-gettext --enable-gather-detailed-mem-stats --with-stabs --enable-debug --enable-largefile --enable-symvers --without-system-zlib --enable-gtk-cairo --enable-gconf-peer --enable-xmlj --enable-gtk-peer --enable-qt-peer --enable-plugin --enable-tool-wrappers --enable-local-sockets --enable-gjdoc --enable-java-awt=gtk,xlib,qt,x --enable-gc-debug --enable-libgcj-debug --enable-objc-gc --enable-libstdcxx-debug --disable-stage1-checking --enable-checking=release --without-system-libunwind --with-gnu-as --with-as=/usr/local/bin/as --with-gnu-ld --with-ld=/usr/local/bin/ld Thread model: posix gcc version 4.4.0 20090117 (experimental) [trunk revision 143454] (GCC) It does matter which options you use since I had 'little trouble' a week ago with few additional ./configure options and 'some trouble' with a few more options added. Now that I've added all these extra options I am at a point where gcc will barely compile with all my available memory. Rob -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38717
next prev parent reply other threads:[~2009-01-17 14:32 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 [this message] 2009-01-17 14:41 ` rob1weld at aol dot com 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=20090117143236.16339.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: linkBe 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).