- Pharo-vm - lists.pharo.org

Nooby questio - getting hello world out of a headless vm
by David Mason Sept. 16, 2022

Sept. 16, 2022

Hi, Iâve built a stackVM straight out of the box from the instructions atÂ https://github.com/pharo-project/pharo-vmÂ to run some experiments. So Iâm trying for a simple Hello world on stdout/stderr. I assumed on headless Transcript would go to some useful place, so I tried, I have a hello.st ----- Transcript show: 'hello world!';cr. "(Smalltalk at: #Transcript) show: 'hello world!';cr." ----- and run-test: ----- #! /bin/sh # # Run it with a headless Pharo: # DIR=~/git/pharo-project/stackVM/build VM=$DIR/vm/Debug/Pharo.app/Contents/MacOS/Pharo #IMAGE=$DIR/dist/pharo-vm/resources/img.image IMAGE=img.image ls -l $VM $IMAGE grep . "$@" /dev/null set -x $VM -vm-display-null -headless --logLevel=4 $IMAGE "$@" --save --quit ----- and I get: : Sep14 ; date;./run-testÂ hello.stÂ ;date Wed 14 Sep 2022 14:09:17 EDT -rwxr-xr-x 1 dmason staff 50226 9 Sep 14:08 /Users/dmason/git/pharo-project/stackVM/build/vm/Debug/Pharo.app/Contents/MacOS/Pharo -rw-r--r-- 1 dmason staff 206336 13 Sep 23:21 img.image hello.st:Transcript show: 'hello world!';cr. hello.st:"(Smalltalk at: #Transcript) show: 'hello world!';cr." + /Users/dmason/git/pharo-project/stackVM/build/vm/Debug/Pharo.app/Contents/MacOS/Pharo -vm-display-null -headless --logLevel=4 img.imageÂ hello.stÂ --save --quit [DEBUG] 2022-09-14 14:09:17.000 logParameters (src/parameters/parameters.c:341):Image file name: img.image [DEBUG] 2022-09-14 14:09:17.000 logParameters (src/parameters/parameters.c:342):Is default Image: no [DEBUG] 2022-09-14 14:09:17.000 logParameters (src/parameters/parameters.c:343):Is interactive session: no [DEBUG] 2022-09-14 14:09:17.000 logParameterVector (src/parameters/parameters.c:331):vmParameters [count = 5]: [DEBUG] 2022-09-14 14:09:17.000 logParameterVector (src/parameters/parameters.c:334): /Users/dmason/git/pharo-project/stackVM/build/vm/Debug/Pharo.app/Contents/MacOS/Pharo [DEBUG] 2022-09-14 14:09:17.000 logParameterVector (src/parameters/parameters.c:334): -vm-display-null [DEBUG] 2022-09-14 14:09:17.000 logParameterVector (src/parameters/parameters.c:334): -headless [DEBUG] 2022-09-14 14:09:17.000 logParameterVector (src/parameters/parameters.c:334): --logLevel=4 [DEBUG] 2022-09-14 14:09:17.000 logParameterVector (src/parameters/parameters.c:334): --headless [DEBUG] 2022-09-14 14:09:17.000 logParameterVector (src/parameters/parameters.c:331):imageParameters [count = 3]: [DEBUG] 2022-09-14 14:09:17.000 logParameterVector (src/parameters/parameters.c:334):Â hello.st [DEBUG] 2022-09-14 14:09:17.000 logParameterVector (src/parameters/parameters.c:334): --save [DEBUG] 2022-09-14 14:09:17.000 logParameterVector (src/parameters/parameters.c:334): --quit [INFO ] 2022-09-14 14:09:17.000 vm_main_with_parameters (src/client.c:113):Opening Image: img.image [DEBUG] 2022-09-14 14:09:17.000 vm_main_with_parameters (src/client.c:135):Working Directory /Users/dmason/git/AST-Smalltalk/testing [DEBUG] 2022-09-14 14:09:17.000 vm_main_with_parameters (src/client.c:137):sizeof(int): 4 [DEBUG] 2022-09-14 14:09:17.000 vm_main_with_parameters (src/client.c:138):sizeof(long): 8 [DEBUG] 2022-09-14 14:09:17.000 vm_main_with_parameters (src/client.c:139):sizeof(long long): 8 [DEBUG] 2022-09-14 14:09:17.000 vm_main_with_parameters (src/client.c:140):sizeof(void*): 8 [DEBUG] 2022-09-14 14:09:17.000 vm_main_with_parameters (src/client.c:141):sizeof(sqInt): 8 [DEBUG] 2022-09-14 14:09:17.000 vm_main_with_parameters (src/client.c:142):sizeof(sqLong): 8 [DEBUG] 2022-09-14 14:09:17.000 vm_main_with_parameters (src/client.c:143):sizeof(float): 4 [DEBUG] 2022-09-14 14:09:17.000 vm_main_with_parameters (src/client.c:144):sizeof(double): 8 [DEBUG] 2022-09-14 14:09:17.000 runOnMainThread (src/client.c:254):Running VM on main thread [DEBUG] 2022-09-14 14:09:17.000 sqAllocateMemory (src/memoryUnix.c:139):Trying to load the image in 0x804000 [DEBUG] 2022-09-14 14:09:17.000 sqAllocateMemory (src/memoryUnix.c:181):Loading the image in 0x106fa4000 [WARN ] 2022-09-14 14:09:17.000 ioLoadModule (src/externalPrimitives.c:102):Failed to load module: SecurityPlugin and 40 minutes later it exits having been kill -9âed Once, it exited quickly, but I have no idea what was different that time. Also âsave does seem to do anything. If it reliably exited, I could experiment, but I have no idea whatâs happening. Help! (and Thanks in advance) ../Dave

3 5

A/B Testing the latest VM on the Pharo repository PRs
by Guillermo Polito Sept. 14, 2022

Sept. 14, 2022

Hi all, TL;DR; I propose we start testing the latest VMs on PRs to the Pharo repository in a "semi-randomâ way. The idea is to earn some confidence while having a small impact on all of you. ==== We need to slowly start pushing the latest VM version, right now hosted in the pharoX branch of the VM repository. This branch so far has all our latest work on the VM for at least one year. Some highlights Interpreter variable auto-localization (Feat/automatic localizationÂ pharo-vm#371 <https://github.com/pharo-project/pharo-vm/pull/371>) Slang cleanups and improvements (Clean slang warningsÂ pharo-vm#413 <https://github.com/pharo-project/pharo-vm/pull/413>, Fix while statement printingÂ pharo-vm#265 <https://github.com/pharo-project/pharo-vm/pull/265>, CastÂ pharo-vm#230 <https://github.com/pharo-project/pharo-vm/pull/230>, Clean slang warningsÂ pharo-vm#413 <https://github.com/pharo-project/pharo-vm/pull/413>, Switch translation to CAST, and testsÂ pharo-vm#311 <https://github.com/pharo-project/pharo-vm/pull/311>, Add several CAST translations and testsÂ pharo-vm#307 <https://github.com/pharo-project/pharo-vm/pull/307>, Fix type inference testsÂ pharo-vm#291 <https://github.com/pharo-project/pharo-vm/pull/291>) SIMD support in the JIT (Speed up object initialization in AArch64 using SIMD instructionsÂ pharo-vm#421 <https://github.com/pharo-project/pharo-vm/pull/421>, SIMD bytecodesÂ pharo-vm#444 <https://github.com/pharo-project/pharo-vm/pull/444>) Initial work on the perm space (Composed image formatÂ pharo-vm#377 <https://github.com/pharo-project/pharo-vm/pull/377>, Composed image format: C translationÂ pharo-vm#388 <https://github.com/pharo-project/pharo-vm/pull/388>, Refactoring of Snapshot and Loading of ImagesÂ pharo-vm#372 <https://github.com/pharo-project/pharo-vm/pull/372>, Perm space on imageÂ pharo-vm#416 <https://github.com/pharo-project/pharo-vm/pull/416>, New & old remembered setsÂ pharo-vm#418 <https://github.com/pharo-project/pharo-vm/pull/418>) Many many bugfixes â¦ To not disrupt anybodyâs work, I propose to make some kind of AB testing on the CI, only impacting PRs to the Pharo repository. odd builds (1,3,5,â¦) use the latest VM even builds (2,4,6,â¦) use the stable VM This will make sure that: the latest VM will be tested in a complex scenario (load code, run testsâ¦) people that have a problem can re-run their builds to get a stable run Iâve made the following PR that follows this idea https://github.com/pharo-project/pharo/pull/11678 G

1 0

https://journal.stuffwithstuff.com/2015/02/01/what-color-is-your-function/
by stephane ducasse Sept. 2, 2022

Sept. 2, 2022

https://journal.stuffwithstuff.com/2015/02/01/what-color-is-your-function/

1 0

Status update of Libgit2 and CI issues
by Guillermo Polito Aug. 19, 2022

Aug. 19, 2022

A couple of weeks ago we got reported a big recurrent failure on CI jobs while cloning using iceberg/libgit https://github.com/pharo-project/pharo/issues/11481. TL;DR; So far (Friday ~17h Paris time) we managed to get everything up and running. A new VM is being released by our CI, all pull requests are issued and we should have everything integrated by tonight. =-=-=-=-=-=-=-= More on the situation: Errors happened randomly with ``` error reading from the zlib stream ``` or ``` bad packet length ``` Several people helped in getting a reliable script to reproduce the issue, plus some instructions to produce a reproduction environment using a docker container. With that in our hands, we managed to corner the issue to a new incompatibility between old libgit2 versions, ssh2, OpenSSL, and (at least) Github. After testing some configurations, we decided to upgrade the libgit and related binaries to newer versions: - libgit 1.4.4 - libssh 1.9.0 - OpenSSL 1.1.1k This was of course not as straightforward as we would have liked. Libgit2 1.4.4 was not compatible with its older versions and broke our ffi bindings. We needed to provide new VM binaries for all our major platforms, make a new VM release, upgrade the libgit2 bindings, and make releases of the libgit2 bindings, iceberg, and backport to Pharo 10 and Pharo 9. TL;DR; So far (Friday ~17h Paris time) we managed to get everything up and running. A new VM is being released by our CI, all pull requests are issued and we should have everything integrated by tonight. Libgit+related compilation instructions are updated in the VM wiki https://github.com/pharo-project/pharo-vm/wiki/Building-OSX-ARM64-Third-Par… https://github.com/pharo-project/pharo-vm/wiki/Building-OSX-X86_64-Third-Pa… https://github.com/pharo-project/pharo-vm/wiki/Building-Linux-ARM64-Third-P… https://github.com/pharo-project/pharo-vm/wiki/Building-Linux-ARM32-Third-P… Libgit bindings Upgrade changes: https://github.com/pharo-vcs/libgit2-pharo-bindings/commit/0e0100f7d0f3a11c… release: https://github.com/pharo-vcs/libgit2-pharo-bindings/releases/tag/v2.2.6 Iceberg Upgrade pr: https://github.com/pharo-vcs/iceberg/pull/1605 release: https://github.com/pharo-vcs/iceberg/releases/tag/v2.0.7 Upgrading library dependencies in the VM https://github.com/pharo-project/pharo-vm/pull/447 Release VM 9.0.16 https://github.com/pharo-project/pharo-vm/releases/tag/v9.0.16 Backports to Pharo Pharo10 https://github.com/pharo-project/pharo/pull/11545 Pharo9 https://github.com/pharo-project/pharo/pull/11546 We have left for later to upgrade library dependencies for the Windows VM (x86-64, ARM64). Of course, any help in this direction is welcome. Cheers, G in behalf of the team

1 0

Fwd: [Pharo-dev] Inovation Technology Award Submission: Polyphemus
by Guillermo Polito Aug. 16, 2022

Aug. 16, 2022

Thanks Pierre, I forward to the Pharo vm list :) > Inicio del mensaje reenviado: > > De: pmissech <pierre.misse-chanabier(a)inria.fr> > Asunto: [Pharo-dev] Inovation Technology Award Submission: Polyphemus > Fecha: 16 de agosto de 2022, 10:36:31 CEST > Para: pharo-users(a)lists.pharo.org, Pharo Development List <pharo-dev(a)lists.pharo.org> > Responder a: Pharo Development List <pharo-dev(a)lists.pharo.org> > > Hello, > > Although i will not be able to attend ESUG'22, a friend agreed to present one of our projects to the innovation award. > **Polyphemus** is a VM related, but public aims at any kind of developers. > Particularly, the video submission talks about how to look at an image and how to **recover** dead images. > Feel free to contact me if you have any questions ! > Enjoy (and vote for Polyphemus!). > > 5 minutes video, Innovation Technology Award submission: https://youtu.be/zf3cCtNW830 > Repository: github.com/hogoww/Polyphemus/ > Additionnal information on image recovery: https://github.com/hogoww/Polyphemus/blob/main/Documentation/ResurrectingDe… > > Cheers !

1 0

MPLR 2022 -- Call for Participation
by Guillermo Polito Aug. 16, 2022

Aug. 16, 2022

======================================================================== Call for Participation MPLR 2022 - 19th International Conference on Managed Programming Languages & Runtimes September 14-15, 2022 in Brussels, Belgium https://soft.vub.ac.be/mplr22/ Follow us @MPLR_Conf ======================================================================== The 19th International Conference on Managed Programming Languages & Runtimes (MPLR, formerly ManLang) is a premier forum for presenting and discussing novel results in all aspects of managed programming languages and runtime systems, which serve as building blocks for some of the most important computing systems in use, ranging from small-scale (embedded and real-time systems) to large-scale (cloud-computing and big-data platforms) and anything in between (desktop, mobile, IoT, and wearable applications). This year, MPLR will be held at the campus of the Vrije Universiteit Brussel(VUB) in Brussels, Belgium. Keynotes -------- Performance Optimizations in the .NET GC Dr. Maoni Stephens, Microsoft, USA Static Compilation of JavaScript Dr. Manuel Serrano, Inria Sophia-Antipolis, France Accepted Papers --------------- Automatic Array Transformation to Columnar Storage at Run Time Lukas Makor et al. Compressed Forwarding Tables Reconsidered Jonas Norlinder et al. Event-Based Out-of-place Debugging Tom Lauwaerts et al. Machine-Learning-Based Self-Optimizing Compiler Heuristics Raphael Mosaner et al. SecSharp: Towards Efficient Trusted Execution in Managed Languages Gilang Mentari Hamidy et al. A Model Checking Framework for a New Collector Framework Bochen Xu et al. Porting a JIT compiler to RISC-V: Challenges and Opportunities Quentin Ducasse et al. Analyzing and Predicting Energy Consumption of Garbage Collectors in OpenJDK Marina Shimchenko et al. Better Understanding the Costs and Benefits of Automatic Memory Management Kunal Sareen et al. Dynamic Taint Analysis with Label-Defined Semantics Jacob Kreindl et al. Attendance ---------- Thanks to our generous sponsors, we were able to significantly reduce this yearâs registration fees. Early Registration Fees: Students: 175 Euro Regular: 250 Euro In addition to the conference participation, the registration includes: - 2-day transportation ticket in the Brussels area - welcome reception on Wednesday, September 14 - guided tour to the city hall and conference banquet on Thursday, September 15 More details, and link to registration system: https://soft.vub.ac.be/mplr22/registration/ Important Dates --------------- Early Registration: 23 August 2022 Conference Dates: 14-15 September 2022

1 0

About global caches
by stephane ducasse July 26, 2022

July 26, 2022

About global lookup caches @Nahuel Palumbo I think we should take a good look at these FIVE papers - Surgical precision JIT compilers [PLDI'14] https://dl.acm.org/doi/10.1145/2666356.2594316 - Efficient late binding of dynamic function compositions https://dl.acm.org/doi/10.1145/3357766.3359543 - Making collection operations optimal with aggressive JIT compilation https://dl.acm.org/doi/10.1145/3136000.3136002 - Dynamic versus Static Optimization Techniques for Object-Oriented Languages https://onlinelibrary.wiley.com/doi/10.1002/j.1096-9942.1995.tb00017.x - A Survey of Adaptive Optimization in Virtual Machines https://ieeexplore.ieee.org/document/1386662

3 2

About IR design: a design overview of javascript cores DFG IR
by stephane ducasse July 26, 2022

July 26, 2022

A design overview of JavaScriptCores DFG IR <https://www.youtube.com/watch?v=EFRzBb9NYjM> https://www.youtube.com/watch?v=EFRzBb9NYjM S

1 0

About MoreVM'22
by stephane ducasse July 26, 2022

July 26, 2022

> Hi! > > Guille and me went to MoreVMs <https://2022.programming-conference.org/home/MoreVMs-2022> event this week. > > We presented > > Interpreter Register Autolocalisation: Improving the performance of efficient interpreters > <autolocalisation.pdf> > > > > > And here there is a summary about the presentations we saw: > > - Less Is More: Merging AST Nodes To Optimize Interpreters > > This presentation shows an optimisation to interpreters merging AST nodes into supernodes, the same idea of superinstructions but at AST level. Itâs implemented on Truffle framework. Now the possible supernodes are selected manually, they have tools to help in this tasks. The results in presented benchmarks show better performance (reducing run time) than without supernodes. > > > - Towards Just-in-time and Language-agnostic Mutation Testing > > This work presents a Mutation Testing framework for languages built using Truffle framework. They offer common language-agnostic mutators and possibility to implement language specific mutators. After that, they perform Mutation Testing using Truffle API to determine the quality of a suite of unit tests. > Iâm not sure why they call âJIT" Mutation Testing. The abstract show the capability to mutate compiled code, take dynamic information at run-time and determine the utility of mutants for skip some of them as techniques with impact in mutant testing efficiency. > > > - Who You Gonna Call? A Case Study about the Call-Site Behaviour in Ruby-on-Rails Applications > > Sophie studied ruby on rails applications to see how many call sites are mono/poly/mega morphic with the objective of observing if they present phased behavior. Phased behavior means that the application behaviour changes at some point during its execution, in which moment it does a change of phase. > > Thing is that call site caches are usually global to the entire lifetime of the application. > However, it may happen that some call-site is monomorphic for some time, then it's monomorphic with another method for some other time. But a normal PIC will make a PIC with two entries instead of resetting the cache and creating monomorphic calls. > > Then she studied how phased behaviour would impact positively some applications. > They then manually marked the start of new phases and observed if the degree of polymorphism got effectively reduced. > > > - Torchy: A Tracing JIT Compiler for PyTorch > > Pytorch is a tool to script machine learning applications in Python that uses the GPU. > The problem of pytorch is that it eagerly performs calls to the GPU for every call in Python, which makes lots of useless roundtrips. > He presented a tracing compiler that creates linear execution traces that are sent all at once to the GPU to avoid such overhead.

1 0

About SIMD [from nico]
by stephane ducasse July 26, 2022

July 26, 2022

â¢ A couple of interesting readings I found today: - SIMD Instructions Considered Harmful https://www.sigarch.org/simd-instructions-considered-harmful/ RISC-V designers explain the disadvantages of fixed-size vector instructions - RISC-V Vector Instructions vs ARM and x86 SIMD https://medium.com/swlh/risc-v-vector-instructions-vs-arm-and-x86-simd-8c9b… Mentions some disadvantages of size-independent vector instructions that are not mentioned in the prior article â¢ Both of these talk about design of CPU instructions, but I think they also apply to bytecode design

1 0