- Pharo-vm - lists.pharo.org

Ephemerons in P11
by Guillermo Polito March 20, 2023

March 20, 2023

Hi all, For those that may not be following the day-to-day development, you may be interested in that Ephemeron support is now enabled in Pharo 11 for one week or so (VM version 10.0.0, Image build 627). Here are some takeaways and actions to take you may be interested in: To get the latest version: - ZeroConf works out of the box - You must update your VMs in the pharo launcher About compatibility: - old images will run on both the old and latest VMs - new images will only run on the latest VM You can read more on: https://github.com/pharo-project/pheps/blob/main/phep-0003.md Cheers, Guille

1 0

pharo-vm-builder
by Guillermo Polito March 15, 2023

March 15, 2023

> El 15 mar. 2023, a las 02:09, HernÃ¡n Morales <hernan-federico.morales(a)inria.fr> escribiÃ³: > > > > De: "Guille Polito" <guillermo.polito(a)inria.fr> > I wonder: > > - how this can get to the mainstream VM > => the graphviz cmake file is nice :) > > I just add a target to the CMakeLists.txt which you can check here (not PR yet): > > https://github.com/pharo-project/pharo-vm/compare/pharo-10...hernanmd:pharo… > > the idea is to configure normally and then launch the install with the target "graphviz" > > cmake --build build --target graphviz Cool! :D Iâm eager to see the PR! Did you check that cmake already has some graphviz support? I did $ cmake âhelp and I saw there is already a âgraphviz option â¦ --graphviz=[file] = Generate graphviz of dependencies, see CMakeGraphVizOptions.cmake for more. â¦ Is there a difference? > > - how can we make the VM configuration step closer to your report > => when we do `cmake -B dir -S source` cmake does a configure step, where it looks for compile time and runtime dependencies, and it prints that to the stdout. We should be able to enhance it to have what you have in the report. > > Another question is maybe to review the defaults of the current configuration? > > Today I checked a bit the CMakeLists.txt and what would be nice is to split (or organize) the file because it's a bit of a bed sheet? Yes, the reality is that we learnt a lot about CMake ***while*** making the CMake configuration of the VM. It was difficult at the beginning because the nice documentation about CMake is a bit scarce. So there are parts that are a bit rough and could be enhanced a lot. Now we know a lot more, but our time is somewhere else... Iâd suggest starting with concrete and small steps. Do some small PRs, they will pass easily :) If you want we can do a fast call and do a code review and identify concrete things to do in this direction! Some ideas are around - using toolchain files, - removing manual compiler options, let CMake do itâs thing - check how to simplify the cygwin builds (that need path conversionsâ¦) - dependency checks could also be done separately - split the compilation of ffi support - then also how plugins are build could be enhanced by a lot using what I drafted for the plugin compilation > > For example, right now the VM build assumes that if youâre in *nix, you will apt-get your libs yourself. > However: > - that does not always work > - Pharo does not nicely report when a lib is missing/not found, so this makes people think âThe VM does not work!" > > I wonder what would be a better default configuration. > > I wonder myself how do you discover the default configuration? It really depends on what you mean by configuration! One way is to look at the CMakeLists.txt. In the first ~30/40 lines we have all options listed. A quick google search tells that doing: cmake -LAH -S source or cmake -LAH buildDirectory prints all options with their default values and description. So it seems itâs just a matter of doing a proper cmake configuration :) > > > Cheers, > > HernÃ¡n > > > El 20 ene. 2023, a las 19:05, HernÃ¡n Morales <hernan-federico.morales(a)inria.fr <mailto:hernan-federico.morales@inria.fr>> escribiÃ³: > > Hi. > > I did a small package to ease VM compilation. Currently it generates: > > - A timestamped build directory for each usage. > - A GraphViz with the Pharo VM dependency graph. > - A compiler commands file (compile_commands.json) to help clangd find include paths in vscode (for this I'm experimenting a bit to see what automated/static checks could bring to the table). > - A timestamped report file with lot of build information for example: > - if we are in docker > - ulimit > - openssl, curl, wgetm git, etc versions > - complete the tree of the build > > The repo: https://github.com/hernanmd/pharo-vm-builder <https://github.com/hernanmd/pharo-vm-builder> > > To use it: > > git clone https://github.com/hernanmd/pharo-vm-builder <https://github.com/hernanmd/pharo-vm-builder> > cd pharo-vm-builder > git clone https://github.com/pharo-project/pharo-vm.git <https://github.com/pharo-project/pharo-vm.git> > ./pharo-vm-builder.sh > > Let me know any other suggestions, > > Cheers, > > HernÃ¡n > > >

1 0

Polyphemus VMIL talk
by Pierre Misse-Chanabier Dec. 27, 2022

Dec. 27, 2022

Hello, I'm quite proud to provide my presentation for the VMIL talk I did on Polyphemus https://www.youtube.com/watch?v=-phxX8ia630. Hope this may be of interest to some of you ! Feel free to ping me for questions :) Cheers ! On 16/08/2022 10:36, pmissech wrote: > 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

Re: [Pharo-dev] Pharo VM Release - v9.0.21
by Guillermo Polito Dec. 12, 2022

Dec. 12, 2022

Thanks Pablo!!! > El 12 dic. 2022, a las 14:30, tesonep(a)gmail.com escribiÃ³: > > Hello, > I have released a new version of the Pharo VM for Pharo 9, Pharo 10 and Pharo 11. This VM is accessible right now from Zero-Conf, updating it in the Pharo Launcher or using the usual downloads (as described in pharo.org/download <http://pharo.org/download>). > > This version includes a series of bug fixes and upgrades on the third-party libraries. > > Changelog: > > - Implementing High resolution clock for ARM64 (Used during profiling) > - Updating third party libraries for all the graphic layer. > - Fixing a performance regression on the allocation of opcodes and fix-ups. > Cleaning only the ones that are going to be used. > Like this, this version has the same speed than before when allocating in the stack. > - Correctly handling the encoding of the command line arguments of the VM (Windows) > - Allocating the opcodes and fixup structs only once and reusing them (Reducing risk of C Stack Overflow) > > Thanks a lot, and any doubt please let me know. > Cheers, > > Pablo on behalf of the whole Pharo team. > > -- > Pablo Tesone. > tesonep(a)gmail.com <mailto:tesonep@gmail.com>

1 0

Looking for an engineer position to work on Virtual Machines
by Pierre Misse-Chanabier Oct. 25, 2022

Oct. 25, 2022

Hello, My name is Pierre Misse-Chanabier. I'm finishing my PhD in the RMOD team on testing Virtual Machines in about two months. I am therefore looking for a Job, hopefully in the Pharo community ! Ideally, I'm looking to work in the domains of Virtual Machines or Language Tooling, or Meta-programing, but I'm open to other opportunities. See my CV attached. I have to stay in Lille for at least the next year, therefore, I am looking to work remotely. Here are my most important projects and publications about them: Illicium : a framework to generate C code from Pharo code. Github repository: [ https://github.com/hogoww/Illicium | https://github.com/hogoww/Illicium ] IWST'19 Illicium: A modular transpilation toolchain from Pharo to C [ https://hal.archives-ouvertes.fr/hal-02297860/ | https://hal.archives-ouvertes.fr/hal-02297860/ ] version poster SAC'22 & full ICSR'22: Differential testing of simulation-based VM generators: automatic detection of VM generator semantic gaps between simulation and generated VMs [ https://link.springer.com/chapter/10.1007/978-3-031-08129-3_7 | https://link.springer.com/chapter/10.1007/978-3-031-08129-3_7 ] [ https://dl.acm.org/doi/abs/10.1145/3477314.3507171 | https://dl.acm.org/doi/abs/10.1145/3477314.3507171 ] Polyphemus: Retro engineering of the Pharo Image, and ease of VM tooling Github Repository: [ https://github.com/hogoww/Polyphemus/ | https://github.com/hogoww/Polyphemus/ ] Video Presentation for Esug Innovation award (I was unable to present it myself): [ https://www.youtube.com/watch?v=zf3cCtNW830 | https://www.youtube.com/watch?v=zf3cCtNW830 ] VMIL'22: Ease VM Level Tooling with Language Level Ordinary Object Pointers [ https://hal.inria.fr/hal-03827632 | https://hal.inria.fr/hal-03827632 ] (preprint) I am particularly interested in my latest work: Polyphemus. I have also worked on many part of the Pharo ecosystem. The Pharo VM, The Pharo bootstrap, Calypso, Debugger, selector extraction, Iceberg scripting, SUnit ... Let me know if you have openings or questions ! Pierre

1 0

Cleaning stale branches
by Guille Polito Oct. 5, 2022

Oct. 5, 2022

We have a couple of stale branches, named a bit chaotically, Iâd like to rename them in a good way, but I donât remember what they are about :) The numbers below (behind | ahead) are according to the current stable pharo9 branch. - headless has already the new tree organisation with cmake - dev-7 and pharo branches have the old tree organisation, dev-7 has some bugfixes when comparing to `pharo` - Cog has the original imported version from monticello Maybe we can have some naming convention for branches? - pharo-[version] to denote major development version branches - feat/[feature] for feature branches if needed Then the four above should be renamed accordingly. Something on the lines of... - Cog -> rename as pharo-0? - pharo -> can be removed - dev-7 -> pharo-1 - headless -> pharo-2 ? G

2 2

Making pharoX the default branch
by Guille Polito Oct. 5, 2022

Oct. 5, 2022

Hi all, We were thinking here with Jean Privat that we could make the pharoX branch (the dev branch) the default branch in the repository. Itâs just a convenience for dev. Thoughts? What should we add in the readme to make sure people do not make mistakes? - say that stable versions are in releases? - say the default branch is always dev? cheers, G & J

4 4

JIT Code Zone
by stephane ducasse Sept. 28, 2022

Sept. 28, 2022

Hello, I am wondering how the Pharo VM and Cogit manage the JIT code zone and have several questions related to that! I will ask my questions and what could be the answers, feel free to correct me! Context: I would like to secure this part of the VM, instrument accesses to it and experiment with changes in its layout/location! Initialization: When and how is the code zone memory allocated? And initialized? The allocation is made through the succession of: allocateMemoryForImage:withHeader: then allocateMemory:desiredPosition:. The initialization is made through initializeCodeZoneFrom:upTo: where trampolines, PIC prototypes and offsets are generated/computed. What is the layout of the different components of the code zone? Trampolines and methods/inline caches coexist, trampolines being the first thing generated. Runtime: JIT compilation - What is the granularity of a JIT compilation? When does it write to machine code? The compiler processes bytecodes at the granularity of a method, using outputInstructionsForGeneratedRuntimeAt: or outputInstructionsAt:. It instruments the actual write with enableCodeZoneWriteDuring:flushingCacheWith:. This step only needs write accesses to the method zone region (after the trampolines). Garbage collection - When is the GC interfering with machine code? For rewriting and compaction? Marking with mapMachineCode: and compaction compactCogCompiledCode are the two ways the GC temper with machine code. While the first one only needs to read data, the second needs both read and write accesses. Interaction between interpreter and machine code - How is forward execution (interpreter - machine code) control flow performed? How is backward execution (machine code - interpreter) performed? I guess the trampolines ceEnterCogCodePopReceiverReg and ceReturnToInterpreter: are the main bridges between both worlds. Bonus: What is the difference between Cogit and the CoInterpreter? Thanks in advance for the answers! <https://www.ensta-bretagne.fr/> <https://www.labsticc.fr/en/index/> Quentin Ducasse Doctorant / PhD Student Lab-STICC â UMR CNRS 6285 www.labsticc.fr ENSTA Bretagne Grande Ã©cole d'ingÃ©nieurs et centre de recherche French State Graduate, Post-Graduate and Research Institute 2 rue FranÃ§ois Verny - 29806 Brest Cedex 9 - France www.ensta-bretagne.fr <https://www.ensta-bretagne.fr/>

2 1

About primitiveMethodXray
by stephane ducasse Sept. 25, 2022

Sept. 25, 2022

Hi In CoInterpreter we can find initializePrimitiveTable super initializePrimitiveTable. PrimNumberHashMultiply := 159. self assert: (PrimitiveTable at: PrimNumberHashMultiply + 1) = #primitiveHashMultiply. #(216 253) do: [:pidx| self assert: (PrimitiveTable at: pidx + 1) = #primitiveFail]. self assert: (PrimitiveTable at: 215 + 1) = #primitiveFlushCacheByMethod. PrimitiveTable at: 253 + 1 put: #primitiveCollectCogCodeConstituents; at: 215 + 1 put: #primitiveVoidVMStateForMethod; at: 216 + 1 put: #primitiveMethodXray There is a primitive primitiveMethodXray :) primitiveMethodXray "Lift the veil from a method and answer an integer describing the interior state of its machine code. Used for e.g. VM tests so they can verify they're testing what they think they're testing. 0 implies a vanilla method. Bit 0 = method might be compiled to machine code Bit 1 = method is currently compiled to machine code Bit 2 = is compiled frameless. Bit 3 = method refers to young object. Bit 4 = method too big to be jitted (more than 64k of code, or needs more than 1.5Mb of stack space to compile) Bit 5 = method contains unknown/unjittable bytecode Bit 6 = method should not be jitted because it contains a primitive not to be called from machine code (unused)" | alreadyCogged flags cogMethod | <var: #cogMethod type: #'CogMethod *'> (self methodWithHeaderShouldBeCogged: (objectMemory methodHeaderOf: self stackTop)) ifTrue: [alreadyCogged := self maybeMethodHasCogMethod: self stackTop. flags := 1. alreadyCogged ifFalse: [cogMethod := cogit cog: self stackTop selector: objectMemory nilObject. (cogMethod = nil and: [cogCompiledCodeCompactionCalledFor]) ifTrue: [self commenceCogCompiledCodeCompaction. cogMethod := cogit cog: self stackTop selector: objectMemory nilObject]. cogMethod asInteger caseOf: { [MethodTooBig] -> [flags := 1 + 16]. [EncounteredUnknownBytecode] -> [flags := 1 + 32]. [ShouldNotJIT] -> [flags := 1 + 64] } otherwise: [self deny: (cogMethod asInteger between: MaxNegativeErrorCode and: NotFullyInitialized)]]. (flags = 1 and: [self maybeMethodHasCogMethod: self stackTop]) ifTrue: [cogMethod := self cogMethodOf: self stackTop. flags := cogMethod stackCheckOffset = 0 ifTrue: [7] ifFalse: [3]. cogMethod cmRefersToYoung ifTrue: [flags := flags + 8]. alreadyCogged ifFalse: [cogit freeMethod: cogMethod]]] ifFalse: [flags := 0]. self pop: 1 thenPush: (objectMemory integerObjectOf: flags) and I wanted to execute it. So on compiledMethod I defined a method CompiledMethod >> xray <primitive: 216> and I did (Point>>#degrees) xray but when I execute I get a compiled method and not an integer. So I probably do something silly. But I would like to understand what. Tx

3 3

Updated plugin compilation info?
by HernÃ¡n Morales Durand Sept. 23, 2022

Sept. 23, 2022

Dear all, I wrote a stupid debugger plugin and generated the C code using: ProtoDebugInterpreterPlugin translateInDirectory: 'ProtoDebug' asFileReference doInlining: false. I remember time ago I modified a plugins.ext file and then copied necessary C headers to a directory (along with my generated .c from Slang) etc etc. Now where should I put my new .c file? Which command/script do you use to compile the VM with a new plugin? Cheers, HernÃ¡n

1 0