public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
* [Bug libgcj/37856]  New: Abort with: Too many heap sections: Increase MAXHINCR or MAX_HEAP_SECTS
@ 2008-10-16 17:58 doko at ubuntu dot com
  0 siblings, 0 replies; only message in thread
From: doko at ubuntu dot com @ 2008-10-16 17:58 UTC (permalink / raw)
  To: java-prs

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


^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2008-10-16 17:58 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-10-16 17:58 [Bug libgcj/37856] New: Abort with: Too many heap sections: Increase MAXHINCR or MAX_HEAP_SECTS doko at ubuntu dot com

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).