>>>> "Hrv" == Hrvoje Niksic
<hniksic(a)srce.hr> writes:
Hrv> Jan Vroonhof <vroonhof(a)math.ethz.ch> writes:
> Olivier Galibert <galibert(a)pobox.com> writes:
>
>
> > 'f' is called. optimize_compiled_function munches the string and
> > replaces it with a (newly allocated) opaque.
>
> Then this is wrong. We must strive for readonlyness. Is there any
> reason we cannot call optimize_compiled_function on all functions
> just before dumping?
Hrv> optimize_compiled_function() is supposed to be lazy. Doing all that
Hrv> works (and allocating all that data) for a bunch of functions that
Hrv> might not get called could be perceived as wasteful.
Hrv> Martin could probably offer a more coherent comment on that.
I believe that when I implemented this, dumped compiled function
objects had already had optimize_compiled_function called for them
prior to dumping. So only functions read into the executable image at
runtime would be lazily optimized.
Martin