Compiling class library with less memory (was: Re: [kaffe] java errors)

[Dalibor Topic]

--- Jim Pick <jim@kaffe.org> wrote:
> > Jim, can I remove the memory constraint for now,
> as
> > long as we have compilation breakage, and don't
> have a
> > better solution than to compile all classes at
> once?
> 
> Sounds OK to me.  I should probably just buy some
> more memory
> for my old NetBSD box.  :-)

My uninformed guess is that the problem source is the
way how kjc compiles all files in a row: first all
files are parsed, then all files are checked, and then
all files are generated. I assume that eats away quite
a bit of memory by just having to keep everything
around until it eventually gets used.

So instead of parsing A, B, C, ... it could parse A,
then parse, check & generate all classes A depends on,
before it comes back to check and generate A. That
would mean that very little memory is devoted to
holding parse trees, because they aren't needed after
they have been used, and they get used quite quickly.

I've approached the kjc developers about this, and
will keep you updated.

best regards,

dalibor topic

__________________________________________________
Do You Yahoo!?
HotJobs - Search Thousands of New Jobs
http://www.hotjobs.com