June 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Improving Pharo By Example

by Gabriel Cotelli

Clean the directory where you're running the script. If some of the files already exists the zero conf script won't work. On Fri, Jun 13, 2014 at 12:14 PM, kilon alios <kilon.alios(a)gmail.com> wrote: > thanks Damien that works. > > However running ./update.sh afterwards creates this error > > "2014-06-13 18:07:52 (1,01 MB/s) - written to stdout [5311/5311] > > Downloading the latest pharoVM: > http://files.pharo.org/vm/pharo/linux/stable.zip > mkdir: cannot create directory âpharo-vmâ: File exists > " > > is this normal ? > > > On Fri, Jun 13, 2014 at 5:17 PM, Damien Cassou <damien.cassou(a)gmail.com> > wrote: > >> On Fri, Jun 13, 2014 at 2:00 PM, kilon alios <kilon.alios(a)gmail.com> >> wrote: >> > So how I proceed ? >> >> >> the Ubuntu PPA is made for this: >> >> sudo add-apt-repository ppa:pharo/stable >> sudo apt-get update >> sudo apt-get install pharo-launcher >> >> Can't be more simple than that >> >> >> >> -- >> Damien Cassou >> http://damiencassou.seasidehosting.st >> >> "Success is the ability to go from one failure to another without >> losing enthusiasm." >> Winston Churchill >> >> >

June 13, 2014

Re: [Pharo-dev] Spur Squeak Trunk Image Available

by Eliot Miranda

Hi Esteban, On Fri, Jun 13, 2014 at 6:31 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > On 13 Jun 2014, at 06:44, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > > On 13 Jun 2014, at 04:29, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > > > On Thu, Jun 12, 2014 at 10:48 PM, stepharo <stepharo(a)free.fr> wrote: > >> Thanks eliot. >> As soon as it is available for Pharo we will try with some large moose >> images. >> > > OK, but just so you know I'm not going to do the Pharo bootstrap. I hope > someone in your team will have a go. I'm happy to help but I don't know > Pharo well enough to do this. It's a matter of making sure the Monticelo > packages can be edited. The Squeak code may just work but I wouldn't know. > > > yes, Iâm on it :) > > > Iâm already building the PharoVM with Spur :) > but thatâs just the beginningâ¦ I need to make it NB compatible first (a > small step, I will finish today or tomorrow) > and I need to convert the imagesâ¦ that will take more time (and I will > need some helpâ¦ cough, cough, Camille, cough, cough, Guille) :P > let me know if I can help... I'm curious whether the basic image bootstrap works out-of-the-box or not (SpurBootstrap bootstrapImage: 'imageBasename'). Yesterday I wrote scripts to automate the Squeak process, and these were used to produce the Squeak trunk Spur image, see http://www.squeakvm.org/svn/squeak/branches/Cog/image/ buildspurtrunkimage.sh BuildSqueakTrunkImage.st WriteSpurPackagesToTempDir.st LoadSpurPackagesFromTempDir.st Most of this is scripting the Monticello package patch and load. Esteban > > > Esteban > > > >> >> Stef >> >> >> On 13/6/14 01:41, Eliot Miranda wrote: >> >>> Hi All, >>> >>> it gives me great pleasure to let you know that a spur-format trunk >>> Squeak image is finally available athttp://www.mirandabanda.org/ >>> files/Cog/SpurImages/. Spur VMs are available at >>> http://www.mirandabanda.org/files/Cog/VM/VM.r2987/. >>> >>> Spur is a new object representation and garbage collector for >>> Squeak/Pharo/Croquet/Newspeak. >>> >>> Features >>> The object representation is significantly simpler than the existing >>> one, and hence permits a lot of JIT optimizations, in particular allocating >>> objects in machine code. This speeds up new, new: et al, but also speeds >>> up blocks because contexts and closures are now allocated in machine code. >>> It also provides immediate characters, so for example accessing wide >>> strings is much faster in Spur, since characters do not have to be >>> instantiated to represent characters with codes greater than 255. >>> >>> The garbage collector has a scavenger and a global scan-mark-compact >>> collector. The scavenger is significantly faster than the existing >>> pointer-reversal scan-mark-compact, hence GC performance is much improved. >>> >>> The memory manager manages old space as a sequence of segments, as >>> opposed to the single contiguous space provided by the existing memory >>> manager. The memory manager grows the heap a segment at a time, and can >>> and will release empty segments back to the host OS after a full GC. Hence >>> Spur is able to grow the heap to the limit of available memory without one >>> having to specify the VM's memory size at start-up. >>> >>> The object representation uses "lazy forwarding" to implement become:, >>> creating copies of objects that are becommed, and forwarding the existing >>> objects to the copies. While Spur still scans the stack zone on become to >>> ensure no forwarding pointers to the receiver exist in stack frames (for >>> check-free push and store instance variable operations), it does not scan >>> the entire heap, catching sends to forwarded objects as part of the normal >>> message send class checks, hence following forwarding pointers lazily, and >>> eliminating forwarders during GC. The existing memory manager does a full >>> memory sweep and compact to implement become. Hence Spur provides the >>> performance advantages of direct pointers while providing a significantly >>> faster become. >>> >>> While Spur uses moving GC (scavenging and compaction on full GC), just >>> like the existing memory manager, Spur supports pinning, the ability to >>> stop an object from moving. Old space objects will not be moved if pinned. >>> Attempting to pin a new space object causes a become, forwarding the new >>> space object to a pinned copy in old space. This allows simpler >>> interfacing with foreign code through the FFI, since one can hand out >>> references to pinned objects in the knowledge that they will not be moved >>> by the GC. >>> >>> Finally Spur supports ephemerons in a simple and direct way, providing >>> pre-mortem per-instance finalization. Although the image-level support >>> needs to be written, it should soon be possible to improve the finalization >>> of entities such as buffered files (ensuring they are flushed before being >>> GCed), etc. >>> >>> >>> Future Work >>> Spur is as yet a work in progress. The 32-bit implementation is usable >>> and appears stable. The major missing component is an incremental >>> scan-mark GC that should eliminate long pauses due to the global >>> scan-mark-compact GC (which is still invoked at snapshot time). I hope to >>> start on this soon. But another key facet of Spur is that the object >>> header format and the sizes of objects are common between 32- and 64-bits. >>> In 32-bit and 64-bit Spur, object bodies are multiples of 8 bytes, so >>> there may be an unused slot at the end of a 32-bit object with an odd >>> number of slots. Hence Spur is close to providing a "true" 64-bit system, >>> one with 61-bit SmallIntegers, and 61-bit SmallFloats (objects with the >>> same precision, but less range that 64-bit Float, done by stealing bits >>> from the exponent field). I look forward to collaborating with Esteban >>> Lorenzano on 64-bit Spur and hope that it will be available early next year. >>> >>> >>> Experience >>> I am of course interested in reports of performance effects. Under >>> certain, hopefully rare circumstances, Spur may actually be slower (one is >>> when the number of processes involved in process switching exceeds the >>> number of stack pages in the stack zone). But my limited experience is >>> that Spur is significantly faster than the existing VM. Please post >>> experiences, both positive and negative. >>> >>> Finally, caveat emptor! This is alpha code. Bugs may result in image >>> corruption. If you do use Spur, please try and back up your work just in >>> case. And if anything does go wrong please let me know, preferrably >>> providing a reproducible case. >>> >>> >>> Enjoy! >>> Eliot Miranda >>> >> >> >> > > > -- > best, > Eliot > > > > -- best, Eliot

June 13, 2014

Re: [Pharo-dev] PharoVM with latests changes

by Sean P. DeNigris

EstebanLM wrote > Soâ¦ last days Iâve been working in new versions of the PharoVM based in > latest Eliot sources. Thanks!! ----- Cheers, Sean -- View this message in context: http://forum.world.st/PharoVM-with-latests-changes-tp4762726p4763000.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

June 13, 2014

Re: [Pharo-dev] Improving Pharo By Example

by kilon alios

thanks Damien that works. However running ./update.sh afterwards creates this error "2014-06-13 18:07:52 (1,01 MB/s) - written to stdout [5311/5311] Downloading the latest pharoVM: http://files.pharo.org/vm/pharo/linux/stable.zip mkdir: cannot create directory âpharo-vmâ: File exists " is this normal ? On Fri, Jun 13, 2014 at 5:17 PM, Damien Cassou <damien.cassou(a)gmail.com> wrote: > On Fri, Jun 13, 2014 at 2:00 PM, kilon alios <kilon.alios(a)gmail.com> > wrote: > > So how I proceed ? > > > the Ubuntu PPA is made for this: > > sudo add-apt-repository ppa:pharo/stable > sudo apt-get update > sudo apt-get install pharo-launcher > > Can't be more simple than that > > > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill > >

June 13, 2014

Re: [Pharo-dev] [rmod] RMoD interview #4

by Marcus Denker

On 11 Jun 2014, at 17:20, Nicolas Petton <petton.nicolas(a)gmail.com> wrote: > Hi! > > I just published another interview of my dear colleagues at RMoD. > This time Jean-Baptiste Arnaud was kind enough to play the game! > > http://nicolas-petton.fr/blog/interview-jean-baptiste.html I added it as a news entry to the RMOD website http://rmod.inria.fr/web/blog/2014-06-13 Marcus

June 13, 2014

Re: [Pharo-dev] Improving Pharo By Example

by Damien Cassou

On Fri, Jun 13, 2014 at 2:00 PM, kilon alios <kilon.alios(a)gmail.com> wrote: > So how I proceed ? the Ubuntu PPA is made for this: sudo add-apt-repository ppa:pharo/stable sudo apt-get update sudo apt-get install pharo-launcher Can't be more simple than that -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

June 13, 2014

Re: [Pharo-dev] Improving Pharo By Example

by Ben Coman

June 13, 2014

Re: [Pharo-dev] Spur Squeak Trunk Image Available

by Esteban Lorenzano

On 13 Jun 2014, at 06:44, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > On 13 Jun 2014, at 04:29, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > >> >> >> On Thu, Jun 12, 2014 at 10:48 PM, stepharo <stepharo(a)free.fr> wrote: >> Thanks eliot. >> As soon as it is available for Pharo we will try with some large moose images. >> >> OK, but just so you know I'm not going to do the Pharo bootstrap. I hope someone in your team will have a go. I'm happy to help but I don't know Pharo well enough to do this. It's a matter of making sure the Monticelo packages can be edited. The Squeak code may just work but I wouldn't know. > > yes, Iâm on it :) Iâm already building the PharoVM with Spur :) but thatâs just the beginningâ¦ I need to make it NB compatible first (a small step, I will finish today or tomorrow) and I need to convert the imagesâ¦ that will take more time (and I will need some helpâ¦ cough, cough, Camille, cough, cough, Guille) :P Esteban > > Esteban > >> >> >> Stef >> >> >> On 13/6/14 01:41, Eliot Miranda wrote: >> Hi All, >> >> it gives me great pleasure to let you know that a spur-format trunk Squeak image is finally available athttp://www.mirandabanda.org/files/Cog/SpurImages/. Spur VMs are available at http://www.mirandabanda.org/files/Cog/VM/VM.r2987/. >> >> Spur is a new object representation and garbage collector for Squeak/Pharo/Croquet/Newspeak. >> >> Features >> The object representation is significantly simpler than the existing one, and hence permits a lot of JIT optimizations, in particular allocating objects in machine code. This speeds up new, new: et al, but also speeds up blocks because contexts and closures are now allocated in machine code. It also provides immediate characters, so for example accessing wide strings is much faster in Spur, since characters do not have to be instantiated to represent characters with codes greater than 255. >> >> The garbage collector has a scavenger and a global scan-mark-compact collector. The scavenger is significantly faster than the existing pointer-reversal scan-mark-compact, hence GC performance is much improved. >> >> The memory manager manages old space as a sequence of segments, as opposed to the single contiguous space provided by the existing memory manager. The memory manager grows the heap a segment at a time, and can and will release empty segments back to the host OS after a full GC. Hence Spur is able to grow the heap to the limit of available memory without one having to specify the VM's memory size at start-up. >> >> The object representation uses "lazy forwarding" to implement become:, creating copies of objects that are becommed, and forwarding the existing objects to the copies. While Spur still scans the stack zone on become to ensure no forwarding pointers to the receiver exist in stack frames (for check-free push and store instance variable operations), it does not scan the entire heap, catching sends to forwarded objects as part of the normal message send class checks, hence following forwarding pointers lazily, and eliminating forwarders during GC. The existing memory manager does a full memory sweep and compact to implement become. Hence Spur provides the performance advantages of direct pointers while providing a significantly faster become. >> >> While Spur uses moving GC (scavenging and compaction on full GC), just like the existing memory manager, Spur supports pinning, the ability to stop an object from moving. Old space objects will not be moved if pinned. Attempting to pin a new space object causes a become, forwarding the new space object to a pinned copy in old space. This allows simpler interfacing with foreign code through the FFI, since one can hand out references to pinned objects in the knowledge that they will not be moved by the GC. >> >> Finally Spur supports ephemerons in a simple and direct way, providing pre-mortem per-instance finalization. Although the image-level support needs to be written, it should soon be possible to improve the finalization of entities such as buffered files (ensuring they are flushed before being GCed), etc. >> >> >> Future Work >> Spur is as yet a work in progress. The 32-bit implementation is usable and appears stable. The major missing component is an incremental scan-mark GC that should eliminate long pauses due to the global scan-mark-compact GC (which is still invoked at snapshot time). I hope to start on this soon. But another key facet of Spur is that the object header format and the sizes of objects are common between 32- and 64-bits. In 32-bit and 64-bit Spur, object bodies are multiples of 8 bytes, so there may be an unused slot at the end of a 32-bit object with an odd number of slots. Hence Spur is close to providing a "true" 64-bit system, one with 61-bit SmallIntegers, and 61-bit SmallFloats (objects with the same precision, but less range that 64-bit Float, done by stealing bits from the exponent field). I look forward to collaborating with Esteban Lorenzano on 64-bit Spur and hope that it will be available early next year. >> >> >> Experience >> I am of course interested in reports of performance effects. Under certain, hopefully rare circumstances, Spur may actually be slower (one is when the number of processes involved in process switching exceeds the number of stack pages in the stack zone). But my limited experience is that Spur is significantly faster than the existing VM. Please post experiences, both positive and negative. >> >> Finally, caveat emptor! This is alpha code. Bugs may result in image corruption. If you do use Spur, please try and back up your work just in case. And if anything does go wrong please let me know, preferrably providing a reproducible case. >> >> >> Enjoy! >> Eliot Miranda >> >> >> >> >> >> -- >> best, >> Eliot >

June 13, 2014

Re: [Pharo-dev] Improving Pharo By Example

by kilon alios

Thanks Ben I tried to install on my new fresh install of UBUNTU 14.04 64 bit and I get all sort of problems. First download.sh does not like the fact that I try to run it from my secondary internal drive and not the home folder. I get permission denied and when I try to turn it to executable , nothing happens, chmod +x executes fine but the file never turns into an executable. Linux is fun :D So i clone it inside the home folder and now even though it is able to run download.sh it gives me an error "Downloading the latest pharoVM: http://files.pharo.org/vm/pharo/linux/stable.zip pharo-vm/pharo Downloading PharoV10.sources: http://files.pharo.org/sources//PharoV10.sources.zip Downloading PharoV20.sources: http://files.pharo.org/sources//PharoV20.sources.zip Downloading PharoV30.sources: http://files.pharo.org/sources//PharoV30.sources.zip Creating starter scripts pharo and pharo-ui Please install the 32bit libraries sudo aptitude install ia32-libs Preparing Pillar image ./pharo: line 11: /home/exloupis/git/UpdatedPharoByExample/pharo-vm/pharo: No such file or directory " I would install the 32bit libs but I thought that those are not necessary for Ubuntu 14 . So how I proceed ? On Mon, Jun 2, 2014 at 5:14 AM, Ben Coman <btc(a)openinworld.com> wrote: > kilon alios wrote: > > ok will do that and you can take it from there and edit it later on if you > want to add additional info. > > > You might reuse what Steph wrote in section 4.3 "Saving a Milestone on > SmalltalkHub" > > https://ci.inria.fr/pharo-contribution/job/PharoLaserGame/17/artifact/Laser… > > > > > On Sun, Jun 1, 2014 at 10:09 PM, Damien Cassou <damien.cassou(a)gmail.com> > wrote: > >> On Sun, Jun 1, 2014 at 8:54 PM, kilon alios <kilon.alios(a)gmail.com> >> wrote: >> > Whats the verdict with the Squeksource section ? Do I covert it to a >> > SmalltalkHub section or do I continue to chapter 4 ? >> >> >> I think you can keep the section about squeaksource and replace it >> with ss3 and smalltalkhub instead. >> >> -- >> Damien Cassou >> http://damiencassou.seasidehosting.st >> >> "Success is the ability to go from one failure to another without >> losing enthusiasm." >> Winston Churchill >> >> > >

June 13, 2014

Re: [Pharo-dev] Performance for Video Games(Woden Video)

by Alexandre Bergel

Currently this only works on Windows and Linux. I will borrow a mac laptop to Ronie to do the port to OSXâ¦ Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. On Jun 13, 2014, at 5:42 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > cool :) > using OSWindow and SDL2, I suppose? > how can I play with that? > > cheers, > Esteban > > On 13 Jun 2014, at 00:16, Ronie Salgado <roniesalg(a)gmail.com> wrote: > >> I am working on making a video game engine in Pharo. Recently added a FPS counter and recorded some samples: http://youtu.be/-2ida5Q1mbg . >> >> Lets say I was quite surprised, so I have yet a lot more to optimize, but a good trick seems to be making some computation in the GPU. >> >> In this video, I show 6 early examples. The water example is still incomplete, missing reflection/refractions, but it shows what happens when I compute the water waves using a shader in the GPU. >> >> Please, pay a close attention to the FPS count. >> >> BTW, it feels slow because of the screen capture and the tearing is there because I haven't enabled vsync, but I have support for it. >> >> Greetings, >> Ronie Salgado >

June 13, 2014