On 19 Jan 2016, at 15:53, Max Leske <maxleske@gmail.com> wrote:

Awesome!! Great work guys!

+ 10

...

On 19 Jan 2016, at 15:29, Christophe Demarey <christophe.demarey@inria.fr> wrote:

Hi all,

In case you do not know, we work on bootstrapping Pharo, i.e. create a Pharo image from sources, not based on a previous image (well, we use a pharo image to produce it but no code / state from it).

This process will allow to define a minimal Pharo kernel (currently 52 packages but we could have it far smaller) and to modularize the whole image (currently packages have too much dependencies on packages already loaded into the image). The bootstrap process also allows to write down the recipe to initialize a new image from scratch (some code is missing in the image or is wrong). In addition, I think we will clean a lot of historical objects that are not used anymore.

With the amazing work done by Guillermo Polito during his Phd (around Espell, Oz): https://guillep.github.io/files/publications/Poli15Thesis.pdf, we succeeded to get a first prototype of a bootstraped Pharo 5 image (from 5.392). This prototype is able to run an eval command line handler and to log output / errors. Not all classes are yet initialized and you cannot yet save / restart this image but it is a big step forward. It is a 4 mb image (could be half the size without unicode data). You can download it at: http://chercheurs.lille.inria.fr/~demarey/pmwiki/pub/pharo-bootstrap/pharo-b....

Next steps are to have a bootstrapped image fully working, then to load packages on top of it (like network, sunit) to produce a minimal image. Then, we need to implement an Oz VM on top of Spur. After that, we need to work on a reliable way to build the bootstrap (not too sensitive to changes in the image).

Christophe.

------- demarey@193-51-236-143:~/dev/rmod/bootstrap/bootstrap-2016-01-19$ ../pharo bootstrap.image --no-default-preferences eval "1 + 1" 2 demarey@193-51-236-143:~/dev/rmod/bootstrap/bootstrap-2016-01-19$ ../pharo bootstrap.image --no-default-preferences eval "'a' , 'b'" 'ab' demarey@193-51-236-143:~/dev/rmod/bootstrap/bootstrap-2016-01-19$ ../pharo bootstrap.image --no-default-preferences eval "1 / 0" ZeroDivide SmallInteger>>/ UndefinedObject>>DoIt OpalCompiler>>evaluate OpalCompiler(AbstractCompiler)>>evaluate: SmalltalkImage>>evaluate:

EvaluateCommandLineHandler>>no (source is Undeclared) no source in EvaluateCommandLineHandler>>evaluate: in Block: no source BlockClosure>>on:do: EvaluateCommandLineHandler>>evaluate: EvaluateCommandLineHandler>>evaluateArguments EvaluateCommandLineHandler>>activate EvaluateCommandLineHandler class(CommandLineHandler class)>>activateWith:

BasicCommandLineHandler>>no (source is Undeclared) no source in PharoCommandLineHandler(BasicCommandLineHandler)>>activateSubCommand: in Block: no source BlockClosure>>on:do: PharoCommandLineHandler(BasicCommandLineHandler)>>activateSubCommand: PharoCommandLineHandler(BasicCommandLineHandler)>>handleSubcommand PharoCommandLineHandler(BasicCommandLineHandler)>>handleArgument:

BasicCommandLineHandler>>no (source is Undeclared) no source in PharoCommandLineHandler(BasicCommandLineHandler)>>activate in Block: no source BlockClosure>>on:do: PharoCommandLineHandler(BasicCommandLineHandler)>>activate PharoCommandLineHandler>>activate PharoCommandLineHandler class(CommandLineHandler class)>>activateWith:

PharoCommandLineHandler class>>no (source is Undeclared) no source in PharoCommandLineHandler class>>activateWith: in Block: no source NonInteractiveUIManager(UIManager)>>defer: PharoCommandLineHandler class>>activateWith: no source in BasicCommandLineHandler>>activateSubCommand: in Block: no source BlockClosure>>on:do: BasicCommandLineHandler>>activateSubCommand: BasicCommandLineHandler>>handleSubcommand BasicCommandLineHandler>>handleArgument: no source in BasicCommandLineHandler>>activate in Block: no source

SmallInteger>>no (source is Undeclared)

UndefinedObject>>no (source is Undeclared)

AbstractCompiler>>no (source is Undeclared)

SmalltalkImage>>no (source is Undeclared)

BlockClosure>>no (source is Undeclared)

EvaluateCommandLineHandler>>no (source is Undeclared)

EvaluateCommandLineHandler>>no (source is Undeclared)

CommandLineHandler class>>no (source is Undeclared)

BasicCommandLineHandler>>no (source is Undeclared)

BasicCommandLineHandler>>no (source is Undeclared)

PharoCommandLineHandler>>no (source is Undeclared)

UIManager>>no (source is Undeclared)

UndefinedObject>>no (source is Undeclared)

CommandLineUIManager>>no (source is Undeclared)

SmalltalkImage>>no (source is Undeclared)

DelayMicrosecondScheduler>>no (source is Undeclared)

BlockClosure>>no (source is Undeclared)

SmalltalkImage>>no (source is Undeclared)

WeakArray class>>no (source is Undeclared)

ps: source cannot be displayed because there is no formatter available in the bootstrap

Oh yes! You cannot imagine all the cleanings that (we they are doing behind your back :) A bootstrap is really a kick in the ass to produce a much much better system. Thanks you guys for making my dream becoming true. Stef Le 19/1/16 16:05, phil@highoctane.be a écrit :

Keep up the good work, this is a huge step in making the whole thing a crystal clear box!

Phil

On Tue, Jan 19, 2016 at 3:29 PM, Christophe Demarey <christophe.demarey@inria.fr <mailto:christophe.demarey@inria.fr>> wrote:

Hi all,

In case you do not know, we work on bootstrapping Pharo, i.e. create a Pharo image from sources, not based on a previous image (well, we use a pharo image to produce it but no code / state from it).

This process will allow to define a minimal Pharo kernel (currently 52 packages but we could have it far smaller) and to modularize the whole image (currently packages have too much dependencies on packages already loaded into the image). The bootstrap process also allows to write down the recipe to initialize a new image from scratch (some code is missing in the image or is wrong). In addition, I think we will clean a lot of historical objects that are not used anymore.

With the amazing work done by Guillermo Polito during his Phd (around Espell, Oz): https://guillep.github.io/files/publications/Poli15Thesis.pdf, *we succeeded to get a first prototype of a bootstraped Pharo 5 image (from 5.392)*. This prototype is able to run an eval command line handler and to log output / errors. Not all classes are yet initialized and you cannot yet save / restart this image but it is a big step forward. It is a 4 mb image (could be half the size without unicode data). You can download it at: http://chercheurs.lille.inria.fr/~demarey/pmwiki/pub/pharo-bootstrap/pharo-b... <http://chercheurs.lille.inria.fr/%7Edemarey/pmwiki/pub/pharo-bootstrap/pharo...>.

Next steps are to have a bootstrapped image fully working, then to load packages on top of it (like network, sunit) to produce a minimal image. Then, we need to implement an Oz VM on top of Spur. After that, we need to work on a reliable way to build the bootstrap (not too sensitive to changes in the image).

Christophe.

------- demarey@193-51-236-143:~/dev/rmod/bootstrap/bootstrap-2016-01-19$ ../pharo bootstrap.image --no-default-preferences eval "1 + 1" 2 demarey@193-51-236-143:~/dev/rmod/bootstrap/bootstrap-2016-01-19$ ../pharo bootstrap.image --no-default-preferences eval "'a' , 'b'" 'ab' demarey@193-51-236-143:~/dev/rmod/bootstrap/bootstrap-2016-01-19$ ../pharo bootstrap.image --no-default-preferences eval "1 / 0" ZeroDivide SmallInteger>>/ UndefinedObject>>DoIt OpalCompiler>>evaluate OpalCompiler(AbstractCompiler)>>evaluate: SmalltalkImage>>evaluate:

EvaluateCommandLineHandler>>no (source is Undeclared) no source in EvaluateCommandLineHandler>>evaluate: in Block: no source BlockClosure>>on:do: EvaluateCommandLineHandler>>evaluate: EvaluateCommandLineHandler>>evaluateArguments EvaluateCommandLineHandler>>activate EvaluateCommandLineHandler class(CommandLineHandler class)>>activateWith:

BasicCommandLineHandler>>no (source is Undeclared) no source in PharoCommandLineHandler(BasicCommandLineHandler)>>activateSubCommand: in Block: no source BlockClosure>>on:do: PharoCommandLineHandler(BasicCommandLineHandler)>>activateSubCommand: PharoCommandLineHandler(BasicCommandLineHandler)>>handleSubcommand PharoCommandLineHandler(BasicCommandLineHandler)>>handleArgument:

BasicCommandLineHandler>>no (source is Undeclared) no source in PharoCommandLineHandler(BasicCommandLineHandler)>>activate in Block: no source BlockClosure>>on:do: PharoCommandLineHandler(BasicCommandLineHandler)>>activate PharoCommandLineHandler>>activate PharoCommandLineHandler class(CommandLineHandler class)>>activateWith:

PharoCommandLineHandler class>>no (source is Undeclared) no source in PharoCommandLineHandler class>>activateWith: in Block: no source NonInteractiveUIManager(UIManager)>>defer: PharoCommandLineHandler class>>activateWith: no source in BasicCommandLineHandler>>activateSubCommand: in Block: no source BlockClosure>>on:do: BasicCommandLineHandler>>activateSubCommand: BasicCommandLineHandler>>handleSubcommand BasicCommandLineHandler>>handleArgument: no source in BasicCommandLineHandler>>activate in Block: no source

SmallInteger>>no (source is Undeclared)

UndefinedObject>>no (source is Undeclared)

AbstractCompiler>>no (source is Undeclared)

SmalltalkImage>>no (source is Undeclared)

BlockClosure>>no (source is Undeclared)

EvaluateCommandLineHandler>>no (source is Undeclared)

EvaluateCommandLineHandler>>no (source is Undeclared)

CommandLineHandler class>>no (source is Undeclared)

BasicCommandLineHandler>>no (source is Undeclared)

BasicCommandLineHandler>>no (source is Undeclared)

PharoCommandLineHandler>>no (source is Undeclared)

UIManager>>no (source is Undeclared)

UndefinedObject>>no (source is Undeclared)

CommandLineUIManager>>no (source is Undeclared)

SmalltalkImage>>no (source is Undeclared)

DelayMicrosecondScheduler>>no (source is Undeclared)

BlockClosure>>no (source is Undeclared)

SmalltalkImage>>no (source is Undeclared)

WeakArray class>>no (source is Undeclared)

ps: source cannot be displayed because there is no formatter available in the bootstrap

Hi Ben, Le 19 janv. 2016 à 17:35, Ben Coman a écrit :

On Tue, Jan 19, 2016 at 10:29 PM, Christophe Demarey <christophe.demarey@inria.fr> wrote:

...

Hi all,

In case you do not know, we work on bootstrapping Pharo, i.e. create a Pharo image from sources, not based on a previous image (well, we use a pharo image to produce it but no code / state from it).

This process will allow to define a minimal Pharo kernel (currently 52 packages but we could have it far smaller) and to modularize the whole image (currently packages have too much dependencies on packages already loaded into the image). The bootstrap process also allows to write down the recipe to initialize a new image from scratch (some code is missing in the image or is wrong). In addition, I think we will clean a lot of historical objects that are not used anymore.

With the amazing work done by Guillermo Polito during his Phd (around Espell, Oz): https://guillep.github.io/files/publications/Poli15Thesis.pdf, we succeeded to get a first prototype of a bootstraped Pharo 5 image (from 5.392). This prototype is able to run an eval command line handler and to log output / errors. Not all classes are yet initialized and you cannot yet save / restart this image but it is a big step forward. It is a 4 mb image (could be half the size without unicode data). You can download it at: http://chercheurs.lille.inria.fr/~demarey/pmwiki/pub/pharo-bootstrap/pharo-b....

Next steps are to have a bootstrapped image fully working, then to load packages on top of it (like network, sunit) to produce a minimal image. Then, we need to implement an Oz VM on top of Spur. After that, we need to work on a reliable way to build the bootstrap (not too sensitive to changes in the image).

Great work guys. Now what stops me feeling compelled to really look deep into this is having a class browser / senders / implementers interface. I guess this is what Oz would facilitate for peeking into the bootstrap image from another image ??

what we have with Espell, are mirrors pointing to the object space we created for the bootstrap. The idea would be to use mirrors in Pharo for all reflective operations to not mix pre-coccupations. Guillermo created this project: http://smalltalkhub.com/#!/~Pharo/Mirrors wit this perspective. Then tools like browser, inspectors, debugger should use these mirrors. Denis is also working to enable remote mirrors (a proxy to a local mirror). With this infrastructure in place, you will be able to browse code from another object space or another image. The bootstrap is a perfect use case to test the work of Denis on remote browsing / debugging. Cheers, Christophe

thanks doru. Yes this is a long term effort :) Le 19/1/16 18:10, Tudor Girba a écrit :

This is amazing news!

For those that might be less involved in this, the minimal image is a long term goal that is essentially in the works since the beginning of Pharo. It accumulated a ton of effort from multiple people (I did not participate, but I have an idea of the amount of effort and it really is huge and tedious), and now we see the first palpable result. This is one of those things that have almost no visible output, but will turn out to have a tremendous impact.

I would like to thank everyone involved! Please do keep this up. Even if it might look less rewarding, you should know that this work is greatly appreciated.

Cheers, Doru

...

On Jan 19, 2016, at 3:29 PM, Christophe Demarey <christophe.demarey@inria.fr> wrote:

Hi all,

In case you do not know, we work on bootstrapping Pharo, i.e. create a Pharo image from sources, not based on a previous image (well, we use a pharo image to produce it but no code / state from it).

This process will allow to define a minimal Pharo kernel (currently 52 packages but we could have it far smaller) and to modularize the whole image (currently packages have too much dependencies on packages already loaded into the image). The bootstrap process also allows to write down the recipe to initialize a new image from scratch (some code is missing in the image or is wrong). In addition, I think we will clean a lot of historical objects that are not used anymore.

With the amazing work done by Guillermo Polito during his Phd (around Espell, Oz): https://guillep.github.io/files/publications/Poli15Thesis.pdf, we succeeded to get a first prototype of a bootstraped Pharo 5 image (from 5.392). This prototype is able to run an eval command line handler and to log output / errors. Not all classes are yet initialized and you cannot yet save / restart this image but it is a big step forward. It is a 4 mb image (could be half the size without unicode data). You can download it at: http://chercheurs.lille.inria.fr/~demarey/pmwiki/pub/pharo-bootstrap/pharo-b....

Next steps are to have a bootstrapped image fully working, then to load packages on top of it (like network, sunit) to produce a minimal image. Then, we need to implement an Oz VM on top of Spur. After that, we need to work on a reliable way to build the bootstrap (not too sensitive to changes in the image).

Christophe.

------- demarey@193-51-236-143:~/dev/rmod/bootstrap/bootstrap-2016-01-19$ ../pharo bootstrap.image --no-default-preferences eval "1 + 1" 2 demarey@193-51-236-143:~/dev/rmod/bootstrap/bootstrap-2016-01-19$ ../pharo bootstrap.image --no-default-preferences eval "'a' , 'b'" 'ab' demarey@193-51-236-143:~/dev/rmod/bootstrap/bootstrap-2016-01-19$ ../pharo bootstrap.image --no-default-preferences eval "1 / 0" ZeroDivide SmallInteger>>/ UndefinedObject>>DoIt OpalCompiler>>evaluate OpalCompiler(AbstractCompiler)>>evaluate: SmalltalkImage>>evaluate:

EvaluateCommandLineHandler>>no (source is Undeclared) no source in EvaluateCommandLineHandler>>evaluate: in Block: no source BlockClosure>>on:do: EvaluateCommandLineHandler>>evaluate: EvaluateCommandLineHandler>>evaluateArguments EvaluateCommandLineHandler>>activate EvaluateCommandLineHandler class(CommandLineHandler class)>>activateWith:

BasicCommandLineHandler>>no (source is Undeclared) no source in PharoCommandLineHandler(BasicCommandLineHandler)>>activateSubCommand: in Block: no source BlockClosure>>on:do: PharoCommandLineHandler(BasicCommandLineHandler)>>activateSubCommand: PharoCommandLineHandler(BasicCommandLineHandler)>>handleSubcommand PharoCommandLineHandler(BasicCommandLineHandler)>>handleArgument:

BasicCommandLineHandler>>no (source is Undeclared) no source in PharoCommandLineHandler(BasicCommandLineHandler)>>activate in Block: no source BlockClosure>>on:do: PharoCommandLineHandler(BasicCommandLineHandler)>>activate PharoCommandLineHandler>>activate PharoCommandLineHandler class(CommandLineHandler class)>>activateWith:

PharoCommandLineHandler class>>no (source is Undeclared) no source in PharoCommandLineHandler class>>activateWith: in Block: no source NonInteractiveUIManager(UIManager)>>defer: PharoCommandLineHandler class>>activateWith: no source in BasicCommandLineHandler>>activateSubCommand: in Block: no source BlockClosure>>on:do: BasicCommandLineHandler>>activateSubCommand: BasicCommandLineHandler>>handleSubcommand BasicCommandLineHandler>>handleArgument: no source in BasicCommandLineHandler>>activate in Block: no source

SmallInteger>>no (source is Undeclared)

UndefinedObject>>no (source is Undeclared)

AbstractCompiler>>no (source is Undeclared)

SmalltalkImage>>no (source is Undeclared)

BlockClosure>>no (source is Undeclared)

EvaluateCommandLineHandler>>no (source is Undeclared)

EvaluateCommandLineHandler>>no (source is Undeclared)

CommandLineHandler class>>no (source is Undeclared)

BasicCommandLineHandler>>no (source is Undeclared)

BasicCommandLineHandler>>no (source is Undeclared)

PharoCommandLineHandler>>no (source is Undeclared)

UIManager>>no (source is Undeclared)

UndefinedObject>>no (source is Undeclared)

CommandLineUIManager>>no (source is Undeclared)

SmalltalkImage>>no (source is Undeclared)

DelayMicrosecondScheduler>>no (source is Undeclared)

BlockClosure>>no (source is Undeclared)

SmalltalkImage>>no (source is Undeclared)

WeakArray class>>no (source is Undeclared)

ps: source cannot be displayed because there is no formatter available in the bootstrap

-- www.tudorgirba.com www.feenk.com

"It's not what we do that matters most, it's how we do it."

Thanks all for your kind words and encouragements! Doru, you're right it has been made possible only because a lot of people took care to clean Pharo time after time*. By example, bootstraping Pharo 2.0 would have been a lot more pain! We can also thanks Pavel for the work he did / does on the minimal image that goes into the same direction. Cheers, Christophe * boy scouts rule: Leave the campground cleaner than you found it. Le 19 janv. 2016 à 18:10, Tudor Girba a écrit :

This is amazing news!

For those that might be less involved in this, the minimal image is a long term goal that is essentially in the works since the beginning of Pharo. It accumulated a ton of effort from multiple people (I did not participate, but I have an idea of the amount of effort and it really is huge and tedious), and now we see the first palpable result. This is one of those things that have almost no visible output, but will turn out to have a tremendous impact.

I would like to thank everyone involved! Please do keep this up. Even if it might look less rewarding, you should know that this work is greatly appreciated.

Cheers, Doru

...

On Jan 19, 2016, at 3:29 PM, Christophe Demarey <christophe.demarey@inria.fr> wrote:

Hi all,

In case you do not know, we work on bootstrapping Pharo, i.e. create a Pharo image from sources, not based on a previous image (well, we use a pharo image to produce it but no code / state from it).

This process will allow to define a minimal Pharo kernel (currently 52 packages but we could have it far smaller) and to modularize the whole image (currently packages have too much dependencies on packages already loaded into the image). The bootstrap process also allows to write down the recipe to initialize a new image from scratch (some code is missing in the image or is wrong). In addition, I think we will clean a lot of historical objects that are not used anymore.

With the amazing work done by Guillermo Polito during his Phd (around Espell, Oz): https://guillep.github.io/files/publications/Poli15Thesis.pdf, we succeeded to get a first prototype of a bootstraped Pharo 5 image (from 5.392). This prototype is able to run an eval command line handler and to log output / errors. Not all classes are yet initialized and you cannot yet save / restart this image but it is a big step forward. It is a 4 mb image (could be half the size without unicode data). You can download it at: http://chercheurs.lille.inria.fr/~demarey/pmwiki/pub/pharo-bootstrap/pharo-b....

Next steps are to have a bootstrapped image fully working, then to load packages on top of it (like network, sunit) to produce a minimal image. Then, we need to implement an Oz VM on top of Spur. After that, we need to work on a reliable way to build the bootstrap (not too sensitive to changes in the image).

Christophe.

------- demarey@193-51-236-143:~/dev/rmod/bootstrap/bootstrap-2016-01-19$ ../pharo bootstrap.image --no-default-preferences eval "1 + 1" 2 demarey@193-51-236-143:~/dev/rmod/bootstrap/bootstrap-2016-01-19$ ../pharo bootstrap.image --no-default-preferences eval "'a' , 'b'" 'ab' demarey@193-51-236-143:~/dev/rmod/bootstrap/bootstrap-2016-01-19$ ../pharo bootstrap.image --no-default-preferences eval "1 / 0" ZeroDivide SmallInteger>>/ UndefinedObject>>DoIt OpalCompiler>>evaluate OpalCompiler(AbstractCompiler)>>evaluate: SmalltalkImage>>evaluate:

EvaluateCommandLineHandler>>no (source is Undeclared) no source in EvaluateCommandLineHandler>>evaluate: in Block: no source BlockClosure>>on:do: EvaluateCommandLineHandler>>evaluate: EvaluateCommandLineHandler>>evaluateArguments EvaluateCommandLineHandler>>activate EvaluateCommandLineHandler class(CommandLineHandler class)>>activateWith:

BasicCommandLineHandler>>no (source is Undeclared) no source in PharoCommandLineHandler(BasicCommandLineHandler)>>activateSubCommand: in Block: no source BlockClosure>>on:do: PharoCommandLineHandler(BasicCommandLineHandler)>>activateSubCommand: PharoCommandLineHandler(BasicCommandLineHandler)>>handleSubcommand PharoCommandLineHandler(BasicCommandLineHandler)>>handleArgument:

BasicCommandLineHandler>>no (source is Undeclared) no source in PharoCommandLineHandler(BasicCommandLineHandler)>>activate in Block: no source BlockClosure>>on:do: PharoCommandLineHandler(BasicCommandLineHandler)>>activate PharoCommandLineHandler>>activate PharoCommandLineHandler class(CommandLineHandler class)>>activateWith:

PharoCommandLineHandler class>>no (source is Undeclared) no source in PharoCommandLineHandler class>>activateWith: in Block: no source NonInteractiveUIManager(UIManager)>>defer: PharoCommandLineHandler class>>activateWith: no source in BasicCommandLineHandler>>activateSubCommand: in Block: no source BlockClosure>>on:do: BasicCommandLineHandler>>activateSubCommand: BasicCommandLineHandler>>handleSubcommand BasicCommandLineHandler>>handleArgument: no source in BasicCommandLineHandler>>activate in Block: no source

SmallInteger>>no (source is Undeclared)

UndefinedObject>>no (source is Undeclared)

AbstractCompiler>>no (source is Undeclared)

SmalltalkImage>>no (source is Undeclared)

BlockClosure>>no (source is Undeclared)

EvaluateCommandLineHandler>>no (source is Undeclared)

EvaluateCommandLineHandler>>no (source is Undeclared)

CommandLineHandler class>>no (source is Undeclared)

BasicCommandLineHandler>>no (source is Undeclared)

BasicCommandLineHandler>>no (source is Undeclared)

PharoCommandLineHandler>>no (source is Undeclared)

UIManager>>no (source is Undeclared)

UndefinedObject>>no (source is Undeclared)

CommandLineUIManager>>no (source is Undeclared)

SmalltalkImage>>no (source is Undeclared)

DelayMicrosecondScheduler>>no (source is Undeclared)

BlockClosure>>no (source is Undeclared)

SmalltalkImage>>no (source is Undeclared)

WeakArray class>>no (source is Undeclared)

ps: source cannot be displayed because there is no formatter available in the bootstrap

-- www.tudorgirba.com www.feenk.com

"It's not what we do that matters most, it's how we do it."

Hi Eliot, Le 19 janv. 2016 à 19:29, Eliot Miranda a écrit :

Hi All,

great news! Where can I read a specification of the Oz VM facilities?

I do not know all the details of the Oz VM but basically, it is a standard stack interpreter vm specialized to be able to run 2 images at the same time on top of it. Guillermo made it possible by using one available bit in the object header of objects to mark the ownership of an object (e.g. is my object from image1 or image2?). Then, he mainly had to specialize VM primitives dealing with objects retrieval from memory. By example, he had to modify the garbage collector to set the right nil instance (yes, we have 2 images so 2 nil instances. we need to take the one of the active image) when an object is garbage collected; the primitive someObject has to return an object from the active image, etc. There is also a way to switch execution from an image to the other just by switching the special objects array reference. You can find some information in: https://guillep.github.io/files/publications/Poli15Thesis.pdf. The Oz code is in http://smalltalkhub.com/#!/~Guille/ObjectSpace and in https://github.com/guillep/OzVM The current implementation uses Cog 6.6.1and OzVM-GuillermoPolito.22. I do not know if Guille has a more formal specification of the Oz VM. If you have advices on what is the best way to handle two distinct object (memory) spaces in Spur, they will be welcomed :) Cheers, Christophe

_,,,^..^,,,_ (phone)

On Jan 19, 2016, at 6:29 AM, Christophe Demarey <christophe.demarey@inria.fr> wrote:

...

Hi all,

In case you do not know, we work on bootstrapping Pharo, i.e. create a Pharo image from sources, not based on a previous image (well, we use a pharo image to produce it but no code / state from it).

This process will allow to define a minimal Pharo kernel (currently 52 packages but we could have it far smaller) and to modularize the whole image (currently packages have too much dependencies on packages already loaded into the image). The bootstrap process also allows to write down the recipe to initialize a new image from scratch (some code is missing in the image or is wrong). In addition, I think we will clean a lot of historical objects that are not used anymore.

With the amazing work done by Guillermo Polito during his Phd (around Espell, Oz): https://guillep.github.io/files/publications/Poli15Thesis.pdf, we succeeded to get a first prototype of a bootstraped Pharo 5 image (from 5.392). This prototype is able to run an eval command line handler and to log output / errors. Not all classes are yet initialized and you cannot yet save / restart this image but it is a big step forward. It is a 4 mb image (could be half the size without unicode data). You can download it at: http://chercheurs.lille.inria.fr/~demarey/pmwiki/pub/pharo-bootstrap/pharo-b....

Next steps are to have a bootstrapped image fully working, then to load packages on top of it (like network, sunit) to produce a minimal image. Then, we need to implement an Oz VM on top of Spur. After that, we need to work on a reliable way to build the bootstrap (not too sensitive to changes in the image).

Christophe.

------- demarey@193-51-236-143:~/dev/rmod/bootstrap/bootstrap-2016-01-19$ ../pharo bootstrap.image --no-default-preferences eval "1 + 1" 2 demarey@193-51-236-143:~/dev/rmod/bootstrap/bootstrap-2016-01-19$ ../pharo bootstrap.image --no-default-preferences eval "'a' , 'b'" 'ab' demarey@193-51-236-143:~/dev/rmod/bootstrap/bootstrap-2016-01-19$ ../pharo bootstrap.image --no-default-preferences eval "1 / 0" ZeroDivide SmallInteger>>/ UndefinedObject>>DoIt OpalCompiler>>evaluate OpalCompiler(AbstractCompiler)>>evaluate: SmalltalkImage>>evaluate:

EvaluateCommandLineHandler>>no (source is Undeclared) no source in EvaluateCommandLineHandler>>evaluate: in Block: no source BlockClosure>>on:do: EvaluateCommandLineHandler>>evaluate: EvaluateCommandLineHandler>>evaluateArguments EvaluateCommandLineHandler>>activate EvaluateCommandLineHandler class(CommandLineHandler class)>>activateWith:

BasicCommandLineHandler>>no (source is Undeclared) no source in PharoCommandLineHandler(BasicCommandLineHandler)>>activateSubCommand: in Block: no source BlockClosure>>on:do: PharoCommandLineHandler(BasicCommandLineHandler)>>activateSubCommand: PharoCommandLineHandler(BasicCommandLineHandler)>>handleSubcommand PharoCommandLineHandler(BasicCommandLineHandler)>>handleArgument:

BasicCommandLineHandler>>no (source is Undeclared) no source in PharoCommandLineHandler(BasicCommandLineHandler)>>activate in Block: no source BlockClosure>>on:do: PharoCommandLineHandler(BasicCommandLineHandler)>>activate PharoCommandLineHandler>>activate PharoCommandLineHandler class(CommandLineHandler class)>>activateWith:

PharoCommandLineHandler class>>no (source is Undeclared) no source in PharoCommandLineHandler class>>activateWith: in Block: no source NonInteractiveUIManager(UIManager)>>defer: PharoCommandLineHandler class>>activateWith: no source in BasicCommandLineHandler>>activateSubCommand: in Block: no source BlockClosure>>on:do: BasicCommandLineHandler>>activateSubCommand: BasicCommandLineHandler>>handleSubcommand BasicCommandLineHandler>>handleArgument: no source in BasicCommandLineHandler>>activate in Block: no source

SmallInteger>>no (source is Undeclared)

UndefinedObject>>no (source is Undeclared)

AbstractCompiler>>no (source is Undeclared)

SmalltalkImage>>no (source is Undeclared)

BlockClosure>>no (source is Undeclared)

EvaluateCommandLineHandler>>no (source is Undeclared)

EvaluateCommandLineHandler>>no (source is Undeclared)

CommandLineHandler class>>no (source is Undeclared)

BasicCommandLineHandler>>no (source is Undeclared)

BasicCommandLineHandler>>no (source is Undeclared)

PharoCommandLineHandler>>no (source is Undeclared)

UIManager>>no (source is Undeclared)

UndefinedObject>>no (source is Undeclared)

CommandLineUIManager>>no (source is Undeclared)

SmalltalkImage>>no (source is Undeclared)

DelayMicrosecondScheduler>>no (source is Undeclared)

BlockClosure>>no (source is Undeclared)

SmalltalkImage>>no (source is Undeclared)

WeakArray class>>no (source is Undeclared)

ps: source cannot be displayed because there is no formatter available in the bootstrap

Cool. Any chance someone can explain for beginners to understand what's going on here? Why is cleaning the image not as simple as running it and deleting any object that wasn't used? (Thanks in advance) On 20 January 2016 at 12:52, Guillermo Polito <guillermopolito@gmail.com> wrote:

Well, there is no formal specification… But I could summarize the features as follows (and as Christophe points mostly out)

OzVM supports having two images in logically separated spaces. This separation is achieved by using the free bit in the object header. Thus we support only two spaces by now.

- The main addition is actually a new primitive: #resumeFromSpecialObjectsArray that receives an special objects array as argument and: - resumes the execution from the active process of such array - on context switch, if the VM is running from a second special objects array, it will return to the first one instead.

- fixes to primitives/bytecodes that assume a single special objects array. e.g., - #someObject and #nextObject should only iterate objects from the correct “space” - #isNil comparisons should take the correct nil - the GC should set the correct nil object on Weak containers

The extensions I made are about 20 overrides to StackPrimitive and NewObjectMemory methods.

The rest is implemented completely on image side. We use mirror primitives to manipulate objects from other space (as each image/space has it’s own selector table).

I have in my long TODO list see if the "clever hack” I did can be supported in a nice manner on top of Spur’s segmented memory. However, I should stop commencing new projects and start finishing them :P.

On 20 ene 2016, at 9:03 a.m., Christophe Demarey <Christophe.Demarey@inria.fr> wrote:

Hi Eliot,

Le 19 janv. 2016 à 19:29, Eliot Miranda a écrit :

Hi All,

great news! Where can I read a specification of the Oz VM facilities?

I do not know all the details of the Oz VM but basically, it is a standard stack interpreter vm specialized to be able to run 2 images at the same time on top of it. Guillermo made it possible by using one available bit in the object header of objects to mark the ownership of an object (e.g. is my object from image1 or image2?). Then, he mainly had to specialize VM primitives dealing with objects retrieval from memory. By example, he had to modify the garbage collector to set the right nil instance (yes, we have 2 images so 2 nil instances. we need to take the one of the active image) when an object is garbage collected; the primitive someObject has to return an object from the active image, etc. There is also a way to switch execution from an image to the other just by switching the special objects array reference.

You can find some information in: https://guillep.github.io/files/publications/Poli15Thesis.pdf. The Oz code is in http://smalltalkhub.com/#!/~Guille/ObjectSpace and in https://github.com/guillep/OzVM The current implementation uses Cog 6.6.1and OzVM-GuillermoPolito.22. I do not know if Guille has a more formal specification of the Oz VM.

If you have advices on what is the best way to handle two distinct object (memory) spaces in Spur, they will be welcomed :)

Cheers, Christophe

_,,,^..^,,,_ (phone)

On Jan 19, 2016, at 6:29 AM, Christophe Demarey <christophe.demarey@inria.fr> wrote:

Hi all,

In case you do not know, we work on bootstrapping Pharo, i.e. create a Pharo image from sources, not based on a previous image (well, we use a pharo image to produce it but no code / state from it).

This process will allow to define a minimal Pharo kernel (currently 52 packages but we could have it far smaller) and to modularize the whole image (currently packages have too much dependencies on packages already loaded into the image). The bootstrap process also allows to write down the recipe to initialize a new image from scratch (some code is missing in the image or is wrong). In addition, I think we will clean a lot of historical objects that are not used anymore.

With the amazing work done by Guillermo Polito during his Phd (around Espell, Oz): https://guillep.github.io/files/publications/Poli15Thesis.pdf, we succeeded to get a first prototype of a bootstraped Pharo 5 image (from 5.392). This prototype is able to run an eval command line handler and to log output / errors. Not all classes are yet initialized and you cannot yet save / restart this image but it is a big step forward. It is a 4 mb image (could be half the size without unicode data). You can download it at: http://chercheurs.lille.inria.fr/~demarey/pmwiki/pub/pharo-bootstrap/pharo-b....

Next steps are to have a bootstrapped image fully working, then to load packages on top of it (like network, sunit) to produce a minimal image. Then, we need to implement an Oz VM on top of Spur. After that, we need to work on a reliable way to build the bootstrap (not too sensitive to changes in the image).

Christophe.

------- demarey@193-51-236-143:~/dev/rmod/bootstrap/bootstrap-2016-01-19$ ../pharo bootstrap.image --no-default-preferences eval "1 + 1" 2 demarey@193-51-236-143:~/dev/rmod/bootstrap/bootstrap-2016-01-19$ ../pharo bootstrap.image --no-default-preferences eval "'a' , 'b'" 'ab' demarey@193-51-236-143:~/dev/rmod/bootstrap/bootstrap-2016-01-19$ ../pharo bootstrap.image --no-default-preferences eval "1 / 0" ZeroDivide SmallInteger>>/ UndefinedObject>>DoIt OpalCompiler>>evaluate OpalCompiler(AbstractCompiler)>>evaluate: SmalltalkImage>>evaluate:

EvaluateCommandLineHandler>>no (source is Undeclared) no source in EvaluateCommandLineHandler>>evaluate: in Block: no source BlockClosure>>on:do: EvaluateCommandLineHandler>>evaluate: EvaluateCommandLineHandler>>evaluateArguments EvaluateCommandLineHandler>>activate EvaluateCommandLineHandler class(CommandLineHandler class)>>activateWith:

BasicCommandLineHandler>>no (source is Undeclared) no source in PharoCommandLineHandler(BasicCommandLineHandler)>>activateSubCommand: in Block: no source BlockClosure>>on:do: PharoCommandLineHandler(BasicCommandLineHandler)>>activateSubCommand: PharoCommandLineHandler(BasicCommandLineHandler)>>handleSubcommand PharoCommandLineHandler(BasicCommandLineHandler)>>handleArgument:

BasicCommandLineHandler>>no (source is Undeclared) no source in PharoCommandLineHandler(BasicCommandLineHandler)>>activate in Block: no source BlockClosure>>on:do: PharoCommandLineHandler(BasicCommandLineHandler)>>activate PharoCommandLineHandler>>activate PharoCommandLineHandler class(CommandLineHandler class)>>activateWith:

PharoCommandLineHandler class>>no (source is Undeclared) no source in PharoCommandLineHandler class>>activateWith: in Block: no source NonInteractiveUIManager(UIManager)>>defer: PharoCommandLineHandler class>>activateWith: no source in BasicCommandLineHandler>>activateSubCommand: in Block: no source BlockClosure>>on:do: BasicCommandLineHandler>>activateSubCommand: BasicCommandLineHandler>>handleSubcommand BasicCommandLineHandler>>handleArgument: no source in BasicCommandLineHandler>>activate in Block: no source

SmallInteger>>no (source is Undeclared)

UndefinedObject>>no (source is Undeclared)

AbstractCompiler>>no (source is Undeclared)

SmalltalkImage>>no (source is Undeclared)

BlockClosure>>no (source is Undeclared)

EvaluateCommandLineHandler>>no (source is Undeclared)

EvaluateCommandLineHandler>>no (source is Undeclared)

CommandLineHandler class>>no (source is Undeclared)

BasicCommandLineHandler>>no (source is Undeclared)

BasicCommandLineHandler>>no (source is Undeclared)

PharoCommandLineHandler>>no (source is Undeclared)

UIManager>>no (source is Undeclared)

UndefinedObject>>no (source is Undeclared)

CommandLineUIManager>>no (source is Undeclared)

SmalltalkImage>>no (source is Undeclared)

DelayMicrosecondScheduler>>no (source is Undeclared)

BlockClosure>>no (source is Undeclared)

SmalltalkImage>>no (source is Undeclared)

WeakArray class>>no (source is Undeclared)

ps: source cannot be displayed because there is no formatter available in the bootstrap

Thanks eliot for this great description.

Guille Polito <guillermopolito@gmail.com> writes:

Just to tell you that I did not forget your email. Since today I'm officially working on this, probably 2-3 days a week. I'll come back with questions/design challenges ;)

welcome back Guille!! -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

I was taking a look at Docker and I was inspired to dream about self contained pharo packages that package their dependencies with them, essentially being isolated and independent , bootstrap is more than welcomed. Keep up the great work :) On Tue, Jan 19, 2016 at 8:54 PM Pavel Krivanek <pavel.krivanek@gmail.com> wrote:

Hi,

amazing! Do you have any idea how to speed up it? The bootstrap process is now running on my machine about one and half hour and it is still far from finish.

Cheers, -- Pavel

2016-01-19 15:29 GMT+01:00 Christophe Demarey <christophe.demarey@inria.fr

...

:

...

Hi all,

In case you do not know, we work on bootstrapping Pharo, i.e. create a Pharo image from sources, not based on a previous image (well, we use a pharo image to produce it but no code / state from it).

This process will allow to define a minimal Pharo kernel (currently 52 packages but we could have it far smaller) and to modularize the whole image (currently packages have too much dependencies on packages already loaded into the image). The bootstrap process also allows to write down the recipe to initialize a new image from scratch (some code is missing in the image or is wrong). In addition, I think we will clean a lot of historical objects that are not used anymore.

With the amazing work done by Guillermo Polito during his Phd (around Espell, Oz): https://guillep.github.io/files/publications/Poli15Thesis.pdf, *we succeeded to get a first prototype of a bootstraped Pharo 5 image (from 5.392)*. This prototype is able to run an eval command line handler and to log output / errors. Not all classes are yet initialized and you cannot yet save / restart this image but it is a big step forward. It is a 4 mb image (could be half the size without unicode data). You can download it at: http://chercheurs.lille.inria.fr/~demarey/pmwiki/pub/pharo-bootstrap/pharo-b... .

Next steps are to have a bootstrapped image fully working, then to load packages on top of it (like network, sunit) to produce a minimal image. Then, we need to implement an Oz VM on top of Spur. After that, we need to work on a reliable way to build the bootstrap (not too sensitive to changes in the image).

Christophe.

------- demarey@193-51-236-143:~/dev/rmod/bootstrap/bootstrap-2016-01-19$ ../pharo bootstrap.image --no-default-preferences eval "1 + 1" 2 demarey@193-51-236-143:~/dev/rmod/bootstrap/bootstrap-2016-01-19$ ../pharo bootstrap.image --no-default-preferences eval "'a' , 'b'" 'ab' demarey@193-51-236-143:~/dev/rmod/bootstrap/bootstrap-2016-01-19$ ../pharo bootstrap.image --no-default-preferences eval "1 / 0" ZeroDivide SmallInteger>>/ UndefinedObject>>DoIt OpalCompiler>>evaluate OpalCompiler(AbstractCompiler)>>evaluate: SmalltalkImage>>evaluate:

EvaluateCommandLineHandler>>no (source is Undeclared) no source in EvaluateCommandLineHandler>>evaluate: in Block: no source BlockClosure>>on:do: EvaluateCommandLineHandler>>evaluate: EvaluateCommandLineHandler>>evaluateArguments EvaluateCommandLineHandler>>activate EvaluateCommandLineHandler class(CommandLineHandler class)>>activateWith:

BasicCommandLineHandler>>no (source is Undeclared) no source in PharoCommandLineHandler(BasicCommandLineHandler)>>activateSubCommand: in Block: no source BlockClosure>>on:do: PharoCommandLineHandler(BasicCommandLineHandler)>>activateSubCommand: PharoCommandLineHandler(BasicCommandLineHandler)>>handleSubcommand PharoCommandLineHandler(BasicCommandLineHandler)>>handleArgument:

BasicCommandLineHandler>>no (source is Undeclared) no source in PharoCommandLineHandler(BasicCommandLineHandler)>>activate in Block: no source BlockClosure>>on:do: PharoCommandLineHandler(BasicCommandLineHandler)>>activate PharoCommandLineHandler>>activate PharoCommandLineHandler class(CommandLineHandler class)>>activateWith:

PharoCommandLineHandler class>>no (source is Undeclared) no source in PharoCommandLineHandler class>>activateWith: in Block: no source NonInteractiveUIManager(UIManager)>>defer: PharoCommandLineHandler class>>activateWith: no source in BasicCommandLineHandler>>activateSubCommand: in Block: no source BlockClosure>>on:do: BasicCommandLineHandler>>activateSubCommand: BasicCommandLineHandler>>handleSubcommand BasicCommandLineHandler>>handleArgument: no source in BasicCommandLineHandler>>activate in Block: no source

SmallInteger>>no (source is Undeclared)

UndefinedObject>>no (source is Undeclared)

AbstractCompiler>>no (source is Undeclared)

SmalltalkImage>>no (source is Undeclared)

BlockClosure>>no (source is Undeclared)

EvaluateCommandLineHandler>>no (source is Undeclared)

EvaluateCommandLineHandler>>no (source is Undeclared)

CommandLineHandler class>>no (source is Undeclared)

BasicCommandLineHandler>>no (source is Undeclared)

BasicCommandLineHandler>>no (source is Undeclared)

PharoCommandLineHandler>>no (source is Undeclared)

UIManager>>no (source is Undeclared)

UndefinedObject>>no (source is Undeclared)

CommandLineUIManager>>no (source is Undeclared)

SmalltalkImage>>no (source is Undeclared)

DelayMicrosecondScheduler>>no (source is Undeclared)

BlockClosure>>no (source is Undeclared)

SmalltalkImage>>no (source is Undeclared)

WeakArray class>>no (source is Undeclared)

ps: source cannot be displayed because there is no formatter available in the bootstrap

On 20 ene 2016, at 9:08 a.m., Christophe Demarey <Christophe.Demarey@inria.fr> wrote:

Hi Pavel,

Le 19 janv. 2016 à 19:53, Pavel Krivanek a écrit :

...

Hi,

amazing! Do you have any idea how to speed up it? The bootstrap process is now running on my machine about one and half hour and it is still far from finish.

The process is indeed far too long (takes around 10 hours) on the CI server. Reasons are: - we use a stack interpreter VM - we modified it and is a bit slower than a classical stack VM

Not quite so. My measurements did not show that… But I can understand the feeling as the StackVM is in general half as fast as the CogVM, which is the VM we are used to use since years.

- we use AST interpretation to build the bootstrap and it is very slow. Guille already did some speed improvements by avoiding to interpret loops by example.

I did not yet spend time on this point because I first wanted to have something working. Definitely, this problem will be tackled when we will put in production the bootstrap.

We should really measure because I see three main aspects: 1) class creation (executes the class builder using AST interpretation) 2) method compilation 3) method installation (using AST interpretation to respect trait copying) My feeling (from what I observe only) is that most of the time is consumed in 2) and 3), and that specially it is in 3). And I particularly want to see how the growing of collections perform.

Cheers, Christophe

...

Cheers, -- Pavel

2016-01-19 15:29 GMT+01:00 Christophe Demarey <christophe.demarey@inria.fr <mailto:christophe.demarey@inria.fr>>: Hi all,

In case you do not know, we work on bootstrapping Pharo, i.e. create a Pharo image from sources, not based on a previous image (well, we use a pharo image to produce it but no code / state from it).

This process will allow to define a minimal Pharo kernel (currently 52 packages but we could have it far smaller) and to modularize the whole image (currently packages have too much dependencies on packages already loaded into the image). The bootstrap process also allows to write down the recipe to initialize a new image from scratch (some code is missing in the image or is wrong). In addition, I think we will clean a lot of historical objects that are not used anymore.

With the amazing work done by Guillermo Polito during his Phd (around Espell, Oz): https://guillep.github.io/files/publications/Poli15Thesis.pdf <https://guillep.github.io/files/publications/Poli15Thesis.pdf>, we succeeded to get a first prototype of a bootstraped Pharo 5 image (from 5.392). This prototype is able to run an eval command line handler and to log output / errors. Not all classes are yet initialized and you cannot yet save / restart this image but it is a big step forward. It is a 4 mb image (could be half the size without unicode data). You can download it at: http://chercheurs.lille.inria.fr/~demarey/pmwiki/pub/pharo-bootstrap/pharo-b... <http://chercheurs.lille.inria.fr/~demarey/pmwiki/pub/pharo-bootstrap/pharo-b...>.

Next steps are to have a bootstrapped image fully working, then to load packages on top of it (like network, sunit) to produce a minimal image. Then, we need to implement an Oz VM on top of Spur. After that, we need to work on a reliable way to build the bootstrap (not too sensitive to changes in the image).

Christophe.

------- demarey@193-51-236-143:~/dev/rmod/bootstrap/bootstrap-2016-01-19$ ../pharo bootstrap.image --no-default-preferences eval "1 + 1" 2 demarey@193-51-236-143:~/dev/rmod/bootstrap/bootstrap-2016-01-19$ ../pharo bootstrap.image --no-default-preferences eval "'a' , 'b'" 'ab' demarey@193-51-236-143:~/dev/rmod/bootstrap/bootstrap-2016-01-19$ ../pharo bootstrap.image --no-default-preferences eval "1 / 0" ZeroDivide SmallInteger>>/ UndefinedObject>>DoIt OpalCompiler>>evaluate OpalCompiler(AbstractCompiler)>>evaluate: SmalltalkImage>>evaluate:

EvaluateCommandLineHandler>>no (source is Undeclared) no source in EvaluateCommandLineHandler>>evaluate: in Block: no source BlockClosure>>on:do: EvaluateCommandLineHandler>>evaluate: EvaluateCommandLineHandler>>evaluateArguments EvaluateCommandLineHandler>>activate EvaluateCommandLineHandler class(CommandLineHandler class)>>activateWith:

BasicCommandLineHandler>>no (source is Undeclared) no source in PharoCommandLineHandler(BasicCommandLineHandler)>>activateSubCommand: in Block: no source BlockClosure>>on:do: PharoCommandLineHandler(BasicCommandLineHandler)>>activateSubCommand: PharoCommandLineHandler(BasicCommandLineHandler)>>handleSubcommand PharoCommandLineHandler(BasicCommandLineHandler)>>handleArgument:

BasicCommandLineHandler>>no (source is Undeclared) no source in PharoCommandLineHandler(BasicCommandLineHandler)>>activate in Block: no source BlockClosure>>on:do: PharoCommandLineHandler(BasicCommandLineHandler)>>activate PharoCommandLineHandler>>activate PharoCommandLineHandler class(CommandLineHandler class)>>activateWith:

PharoCommandLineHandler class>>no (source is Undeclared) no source in PharoCommandLineHandler class>>activateWith: in Block: no source NonInteractiveUIManager(UIManager)>>defer: PharoCommandLineHandler class>>activateWith: no source in BasicCommandLineHandler>>activateSubCommand: in Block: no source BlockClosure>>on:do: BasicCommandLineHandler>>activateSubCommand: BasicCommandLineHandler>>handleSubcommand BasicCommandLineHandler>>handleArgument: no source in BasicCommandLineHandler>>activate in Block: no source

SmallInteger>>no (source is Undeclared)

UndefinedObject>>no (source is Undeclared)

AbstractCompiler>>no (source is Undeclared)

SmalltalkImage>>no (source is Undeclared)

BlockClosure>>no (source is Undeclared)

EvaluateCommandLineHandler>>no (source is Undeclared)

EvaluateCommandLineHandler>>no (source is Undeclared)

CommandLineHandler class>>no (source is Undeclared)

BasicCommandLineHandler>>no (source is Undeclared)

BasicCommandLineHandler>>no (source is Undeclared)

PharoCommandLineHandler>>no (source is Undeclared)

UIManager>>no (source is Undeclared)

UndefinedObject>>no (source is Undeclared)

CommandLineUIManager>>no (source is Undeclared)

SmalltalkImage>>no (source is Undeclared)

DelayMicrosecondScheduler>>no (source is Undeclared)

BlockClosure>>no (source is Undeclared)

SmalltalkImage>>no (source is Undeclared)

WeakArray class>>no (source is Undeclared)

ps: source cannot be displayed because there is no formatter available in the bootstrap

reducing also the number of classes in the kernel could help. But first it should work and then we start to optimize Now this is true that 10 h is insane :) Le 20/1/16 09:08, Christophe Demarey a écrit :

Hi Pavel,

Le 19 janv. 2016 à 19:53, Pavel Krivanek a écrit :

...

Hi,

amazing! Do you have any idea how to speed up it? The bootstrap process is now running on my machine about one and half hour and it is still far from finish.

The process is indeed far too long (takes around 10 hours) on the CI server. Reasons are: - we use a stack interpreter VM - we modified it and is a bit slower than a classical stack VM - we use AST interpretation to build the bootstrap and it is very slow. Guille already did some speed improvements by avoiding to interpret loops by example.

I did not yet spend time on this point because I first wanted to have something working. Definitely, this problem will be tackled when we will put in production the bootstrap.

Cheers, Christophe

...

Cheers, -- Pavel

2016-01-19 15:29 GMT+01:00 Christophe Demarey <christophe.demarey@inria.fr <mailto:christophe.demarey@inria.fr>>:

Hi all,

In case you do not know, we work on bootstrapping Pharo, i.e. create a Pharo image from sources, not based on a previous image (well, we use a pharo image to produce it but no code / state from it).

This process will allow to define a minimal Pharo kernel (currently 52 packages but we could have it far smaller) and to modularize the whole image (currently packages have too much dependencies on packages already loaded into the image). The bootstrap process also allows to write down the recipe to initialize a new image from scratch (some code is missing in the image or is wrong). In addition, I think we will clean a lot of historical objects that are not used anymore.

With the amazing work done by Guillermo Polito during his Phd (around Espell, Oz): https://guillep.github.io/files/publications/Poli15Thesis.pdf, *we succeeded to get a first prototype of a bootstraped Pharo 5 image (from 5.392)*. This prototype is able to run an eval command line handler and to log output / errors. Not all classes are yet initialized and you cannot yet save / restart this image but it is a big step forward. It is a 4 mb image (could be half the size without unicode data). You can download it at: http://chercheurs.lille.inria.fr/~demarey/pmwiki/pub/pharo-bootstrap/pharo-b... <http://chercheurs.lille.inria.fr/%7Edemarey/pmwiki/pub/pharo-bootstrap/pharo...>.

Next steps are to have a bootstrapped image fully working, then to load packages on top of it (like network, sunit) to produce a minimal image. Then, we need to implement an Oz VM on top of Spur. After that, we need to work on a reliable way to build the bootstrap (not too sensitive to changes in the image).

Christophe.

------- demarey@193-51-236-143:~/dev/rmod/bootstrap/bootstrap-2016-01-19$ ../pharo bootstrap.image --no-default-preferences eval "1 + 1" 2 demarey@193-51-236-143:~/dev/rmod/bootstrap/bootstrap-2016-01-19$ ../pharo bootstrap.image --no-default-preferences eval "'a' , 'b'" 'ab' demarey@193-51-236-143:~/dev/rmod/bootstrap/bootstrap-2016-01-19$ ../pharo bootstrap.image --no-default-preferences eval "1 / 0" ZeroDivide SmallInteger>>/ UndefinedObject>>DoIt OpalCompiler>>evaluate OpalCompiler(AbstractCompiler)>>evaluate: SmalltalkImage>>evaluate:

EvaluateCommandLineHandler>>no (source is Undeclared) no source in EvaluateCommandLineHandler>>evaluate: in Block: no source BlockClosure>>on:do: EvaluateCommandLineHandler>>evaluate: EvaluateCommandLineHandler>>evaluateArguments EvaluateCommandLineHandler>>activate EvaluateCommandLineHandler class(CommandLineHandler class)>>activateWith:

BasicCommandLineHandler>>no (source is Undeclared) no source in PharoCommandLineHandler(BasicCommandLineHandler)>>activateSubCommand: in Block: no source BlockClosure>>on:do: PharoCommandLineHandler(BasicCommandLineHandler)>>activateSubCommand: PharoCommandLineHandler(BasicCommandLineHandler)>>handleSubcommand PharoCommandLineHandler(BasicCommandLineHandler)>>handleArgument:

BasicCommandLineHandler>>no (source is Undeclared) no source in PharoCommandLineHandler(BasicCommandLineHandler)>>activate in Block: no source BlockClosure>>on:do: PharoCommandLineHandler(BasicCommandLineHandler)>>activate PharoCommandLineHandler>>activate PharoCommandLineHandler class(CommandLineHandler class)>>activateWith:

PharoCommandLineHandler class>>no (source is Undeclared) no source in PharoCommandLineHandler class>>activateWith: in Block: no source NonInteractiveUIManager(UIManager)>>defer: PharoCommandLineHandler class>>activateWith: no source in BasicCommandLineHandler>>activateSubCommand: in Block: no source BlockClosure>>on:do: BasicCommandLineHandler>>activateSubCommand: BasicCommandLineHandler>>handleSubcommand BasicCommandLineHandler>>handleArgument: no source in BasicCommandLineHandler>>activate in Block: no source

SmallInteger>>no (source is Undeclared)

UndefinedObject>>no (source is Undeclared)

AbstractCompiler>>no (source is Undeclared)

SmalltalkImage>>no (source is Undeclared)

BlockClosure>>no (source is Undeclared)

EvaluateCommandLineHandler>>no (source is Undeclared)

EvaluateCommandLineHandler>>no (source is Undeclared)

CommandLineHandler class>>no (source is Undeclared)

BasicCommandLineHandler>>no (source is Undeclared)

BasicCommandLineHandler>>no (source is Undeclared)

PharoCommandLineHandler>>no (source is Undeclared)

UIManager>>no (source is Undeclared)

UndefinedObject>>no (source is Undeclared)

CommandLineUIManager>>no (source is Undeclared)

SmalltalkImage>>no (source is Undeclared)

DelayMicrosecondScheduler>>no (source is Undeclared)

BlockClosure>>no (source is Undeclared)

SmalltalkImage>>no (source is Undeclared)

WeakArray class>>no (source is Undeclared)

ps: source cannot be displayed because there is no formatter available in the bootstrap