Cache the "base" sysimage using Scratch.jl about packagecompiler.jl HOT 3 OPEN

That would be a great feature to have! It slightly relates to some of the suggestions in #858. One question that was hard for me to answer though, is how to ensure that the correct cached base sysimage is determined based on the Julia flags (and other environmental variables?). I am thinking that things like -O3 or --check-bounds=yes|no would probably result in different base images.

Also, given that there is (likely) a myriad of different combinations, do we only want to keep the latest cache image or one for each possible feature set? Also, how to prevent race conditions during generation?

from packagecompiler.jl.

I think it is fine for code in Base to be compiled with the default arguments. The app/library specific code will then be compiled with whatever specific options are given.

The CPU-target has to be correct though I think.

Also, how to prevent race conditions during generation?

We could have a PID lock for the sysimage being generated.

from packagecompiler.jl.

I think it is fine for code in Base to be compiled with the default arguments

OK, this makes sense.

We could have a PID lock for the sysimage being generated.

Sounds good.

In general, if we add such a caching feature, it would be good if we can add functions to also remove the cached file and/or force the regeneration of a new file upon next use.

from packagecompiler.jl.