public inbox for java-prs@sourceware.org help / color / mirror / Atom feed
From: "doko at ubuntu dot com" <gcc-bugzilla@gcc.gnu.org> To: java-prs@gcc.gnu.org Subject: [Bug libgcj/37856] New: Abort with: Too many heap sections: Increase MAXHINCR or MAX_HEAP_SECTS Date: Thu, 16 Oct 2008 17:58:00 -0000 [thread overview] Message-ID: <bug-37856-11764@http.gcc.gnu.org/bugzilla/> (raw) see PR37855 for the use case (building icedtea --with-alt-jar=gjar $ /usr/bin/gjar c0mf /scratch/packages/openjdk/d/icedtest/openjdk/control/build/linux-i586/tmp/manifest.tmp /scratch/packages/openjdk/d/icedtest/openjdk/control/build/linux-i586/tmp/rt-orig.jar @/scratch/packages/openjdk/d/icedtest/openjdk/control/build/linux-i586/tmp/jarfilelists/rt_jar_list_args -J-client -J-Xmx896m -J-Xms128m -J-XX:PermSize=32m -J-XX:MaxPermSize=160m Too many heap sections: Increase MAXHINCR or MAX_HEAP_SECTS Aborted In the past there was some dicussion about setting LARGE_CONFIG, see http://gcc.gnu.org/ml/java-patches/2005-q4/msg00149.html and in the followup: "For the branch, I wanted to solve the problem while making the least intrusive change possible. On HEAD, it sounds like LARGE_CONFIG is the way to go. I will test a patch shortly and reverse the MAX_ROOT_SETS change there." -- Summary: Abort with: Too many heap sections: Increase MAXHINCR or MAX_HEAP_SECTS Product: gcc Version: 4.4.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libgcj AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: doko at ubuntu dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37856
reply other threads:[~2008-10-16 17:58 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-37856-11764@http.gcc.gnu.org/bugzilla/ \ --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).