make bootstrap

make bootstrap

[Fabrice Popineau]

I was trying to squeez as much as possible the data to be dumped.
While doing this I noticed that to be able to 'make bootstrap', I need a much 
larger area than for building a regular emacs.
Why is this ? I would have expect to build the very same temacs for 
bootstraping.

For a w64 emacs, I need 18Mb for bootstraping and only 10Mb for a regular 
emacs.

It is also possible that I am missing somehting there.
Thanks for clarification.

Fabrice

Re: make bootstrap

[David Kastrup]

Fabrice Popineau <fabrice.popineau@gmail.com> writes:

> I was trying to squeez as much as possible the data to be dumped.
> While doing this I noticed that to be able to 'make bootstrap', I need a much 
> larger area than for building a regular emacs.
> Why is this ? I would have expect to build the very same temacs for 
> bootstraping.
>
> For a w64 emacs, I need 18Mb for bootstraping and only 10Mb for a regular 
> emacs.
>
> It is also possible that I am missing somehting there.
> Thanks for clarification.

Bootstrapping does not garbage-collect if I remember correctly.  It
might be worth checking which part of the bootstrap causes the majority
of garbage and see whether one can avoid more of it.

-- 
David Kastrup

Re: make bootstrap

[Andreas Schwab]

Fabrice Popineau <fabrice.popineau@gmail.com> writes:

> While doing this I noticed that to be able to 'make bootstrap', I need a much 
> larger area than for building a regular emacs.
> Why is this ?

Because it's using the non-compiled lisp files for bootstrap-emacs.

Andreas.

-- 
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."

Re: make bootstrap

[Fabrice Popineau]

Andreas Schwab <schwab <at> suse.de> writes:

> 
> Fabrice Popineau <fabrice.popineau <at> gmail.com> writes:
> 
> > While doing this I noticed that to be able to 'make bootstrap', I need a 
much 
> > larger area than for building a regular emacs.
> > Why is this ?
> 
> Because it's using the non-compiled lisp files for bootstrap-emacs.
> 

Oops. That might be a good reason!

Currently, the size for these dumped data is hardwired in the build process.
I'll try to find a way to make it more configurable (at least for the w64 
case).

Thanks.

Fabrice

Re: make bootstrap

[Eli Zaretskii]

> From: Fabrice Popineau <fabrice.popineau@gmail.com>
> Date: Mon, 3 Mar 2014 11:53:41 +0000 (UTC)
> 
> Andreas Schwab <schwab <at> suse.de> writes:
> 
> > 
> > Fabrice Popineau <fabrice.popineau <at> gmail.com> writes:
> > 
> > > While doing this I noticed that to be able to 'make bootstrap', I need a 
> much 
> > > larger area than for building a regular emacs.
> > > Why is this ?
> > 
> > Because it's using the non-compiled lisp files for bootstrap-emacs.
> > 
> 
> Oops. That might be a good reason!
> 
> Currently, the size for these dumped data is hardwired in the build process.
> I'll try to find a way to make it more configurable (at least for the w64 
> case).

There is an alternative: if you run out of space, malloc some buffer
and continue allocating from the heap.  This is what pure_alloc does.
The reason is that bootstrap-emacs is only used to byte-compile a
relatively small number of Lisp files, those which are preloaded.
Once those are compiled, we re-dump Emacs using the byte-compiled
files, then use that for the rest of the bootstrap (and for future
builds in the same tree).  So it is not important that some of the
loaded files in bootstrap-emacs are in a static array, while others
are on the heap.  I think.