This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Failure to build libjava on 512MB machine
Marco Trudel writes:
> Andrew Haley wrote:
> > Gerald Pfeifer writes:
> > > I can no longer build libjava on a machine with "just" 512MB of main
> > > memory (FreeBSD/i386 5.4 in this case).
> > >
> > > Three weeks ago the build worked on that very machine; did we raise
> > > our minimum requirements
> >
> > We just imported a whole new release of the Classpath library, and
> > it's big. But that doesn't explain this bug.
>
> You mean 0.93, right?
Strictly speaking it's the (former) generics branch from Classpath,
but yes.
> > > or is this simply a bug?
> >
> > I think so. javax/swing/text/html/parser is quite small:
> >
> > $ /usr/bin/time make javax/swing/text/html/parser.lo
>
> What? No way! I always thought this must be something about 7gb or so.
> Compiling my canadian cross mingw takes 2h. 40min to 50min is spend for
> compiling html/parser...
> I think a linux normal build (static, 32bit) also needs about 2h. A
> cross host=mingw target=linux took only 50min to my surprise.
> > 0.53user 0.16system 0:00.74elapsed 93%CPU (0avgtext+0avgdata 0maxresident)k
> > 0inputs+0outputs (0major+26369minor)pagefaults 0swaps
> >
> > $ ls -lh javax/swing/text/html/.libs/parser.o
> > -rw-r--r-- 1 aph aph 260K Jan 30 11:44 javax/swing/text/html/.libs/parser.o
> >
> > I don't know why it is using so much memory in your case.
>
> I assume is has something to do with optimization.
I think I was compiling the wrong file. There's
gnu/javax/swing/text/html/parser.lo and
javax/swing/text/html/partser.lo, which is much larger. Sorry.
Anyway, I tried again, this time with the right file, and it took
78.67user 1.29system 1:20.01elapsed 99%CPU (0avgtext+0avgdata 0maxresident)k
and indeed, it does want a lot of memory - at peak some 550m. It'll
be smaller on a 32-bit box, but not much smaller.
Andrew.