October 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Pharo-users] [ANN] Cupboard inspector for Teapot

by Tudor Girba

You really are having fun :). Nice! Doru On Mon, Oct 12, 2015 at 3:37 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > Hi, > > I took a few minutes to add a custom inspector tool ("Cupboard") to > Teapot showing all the available teapots. The tool is accessible from the > Tool menu right after loading "Teapot" and allows get an overview on > running teapots. > If you teapot has dynamic routes they will be shown as well. See screenshot > attached. > > You can also start/stop a Teapot or add a new one serving static > contents from a selected directory. > > Also catalog messages were added to the ConfigurationOfTeapot and the > NeoJSON repo in the dependencies was fixed. > > Just get the lates stable version: > > Gofer it > smalltalkhubUser: 'zeroflag' project: 'Teapot'; > configuration; > loadStable. > > or directly load from ConfigBrowser (Pharo 4) or CatalogBrowser/Spotter > (Pharo 5) > in a fresh image. > > > If you want to quickly serve a (static) webpage from Pharo > ========================================================== > Create a web directory and HTML page > - use "Tools" -> "File Browser" > - create a directory "www" using "Add new directory", navigate to it > - create a new file "index.html" using "Add new file", edit it and > accept the changes > > Serve it from Pharo > - load Teapot in a fresh image > - open "Tools" -> "Teapot" > - click on the server icon on the right to create a new static server > - accept the default port 80 or enter a new one > - select the directory > > Point your browser to http://localhost:80 > > If you want to quickly server (dynamic) content from Pharo: > =========================================================== > - use one of the examples on http://smalltalkhub.com/#!/~zeroflag/Teapot > Note that the dynamic routes are shown in the new tool > > Tip: if you like use "Mustache" template library to mix HTML content > (like Bootstrap templates, Material design templates or other > with your Pharo server objects to serve pages) > > Have fun > T. -- www.tudorgirba.com "Every thing has its own flow"

Oct. 12, 2015

Re: [Pharo-dev] Problems with a large block

by Henrik Johansen

> On 10 Oct 2015, at 10:05 , Nicolai Hess <nicolaihess(a)web.de> wrote: > > > > 2015-10-08 23:45 GMT+02:00 Eliot Miranda <eliot.miranda(a)gmail.com <mailto:eliot.miranda@gmail.com>>: > Hi Nicolai, > > On Thu, Oct 8, 2015 at 2:27 PM, Nicolai Hess <nicolaihess(a)web.de <mailto:nicolaihess@web.de>> wrote: > Hello Eliot, and thanks for your time. > > > In our (pharo) implementation for sourceNodeForPC, we start at the AST-Node of > the compiled method, get the IR (IntermediateRepresentation) and scan this sequence of IRNodes > until we finally find that one, that maps to the bytecode of the closure creation code (this should be a IRPushClosureCopy). > The problem is now, we don't find (always) the right IRNode, and it depens on the number of local temps, if this is > 3 we don't hit the right one. > > That's very strange. Can you construct a synthetic example of two simple blocks, one with three temps and and one with four temps and show me the difference in the byte code? > > > [ :x | | a b c | a:=b:=c:=x ] "calling #sourceNode gives a RBBlockNode - ok" > Bytecode > 13 <8F 01 00 0B> closureNumCopied: 0 numArgs: 1 bytes 17 to 27 > 17 <73> pushConstant: nil > 18 <73> pushConstant: nil > 19 <73> pushConstant: nil > 20 <10> pushTemp: 0 > 21 <81 43> storeIntoTemp: 3 > 23 <81 42> storeIntoTemp: 2 > 25 <81 41> storeIntoTemp: 1 > 27 <7D> blockReturn > 28 <7C> returnTop > > > [ :x | | a b c d | a:=b:=c:=d:=x ] "calling #sourceNode gives a RBMethodNode - not ok" > Bytecode > 13 <8F 01 00 0E> closureNumCopied: 0 numArgs: 1 bytes 17 to 30 > 17 <73> pushConstant: nil > 18 <73> pushConstant: nil > 19 <73> pushConstant: nil > 20 <73> pushConstant: nil > 21 <10> pushTemp: 0 > 22 <81 44> storeIntoTemp: 4 > 24 <81 43> storeIntoTemp: 3 > 26 <81 42> storeIntoTemp: 2 > 28 <81 41> storeIntoTemp: 1 > 30 <7D> blockReturn > 31 <7C> returnTop > > As I wrote above, in Pharo, to get the sourceNode we try to find the push closure bytecode from "startpc - 1" by traversing > the IR and try to get the IRNode with matching "bytecodeOffset". The bytecodeOffsets for the above blocks: > > [ :x | | a b c | a:=b:=c:=x ] > "bytecodeOffset -> IR" > 19->pushClosureCopyCopiedValues: #() args: #(#x) > 28->returnTop > 20->pushTemp: #x > 22->storeTemp: #c > 24->storeTemp: #b > 26->storeTemp: #a > 27->blockReturnTop > > [ :x | | a b c d | a:=b:=c:=d:=x ] > "bytecodeOffset -> IR" > 20->pushClosureCopyCopiedValues: #() args: #(#x) > 31->returnTop > 21->pushTemp: #x > 23->storeTemp: #d > 25->storeTemp: #c > 27->storeTemp: #b > 29->storeTemp: #a > 30->blockReturnTop > > Both blocks don't have a bytecodeOffset matching the bytecode of the pushclosure (13), but we start the search from "startpc - 1" (= 16) > and do a loop from 0 to -3 (because bytecodes can have a length of 1,2 or 4) > For the first block, this works > bytecodeOffset 19 = 16 - (-3) > For the second block this does not work, somehow the bytecodeoffset value depends on the number of local temps. And for the > second block this is one greater. > > > > > And my interpretation was, the IRPushClosureCopy node has the wrong "bytecode offset" (whatever this is). The bytecodeOffset value (somehow) > depends on the number of local temps, but maybe this is right (for whatever this is used) and we are just using it wrong for in this situation. > > So you need to ask Marcus how to interpret bytecodeOffset. The thing is, it should be simple. One has: > > BlockCreationBytecode > any number of pushConstant: nil's (0 to N) > first byte code in block > last bytecode in block (always a blockReturnTop) > > and a block's startup is always that of the byte immediately following the BlockCreationBytecode. So if the byte code offset is somehow the span of the "any number of pushConstant: nil's (0 to N)" then there's a bug in the IR somewhere when the number of temps is > 3. But if that's not what it means then, well, I don't know what the problem is. > For some reason, bytecodeOffset is the *last* byte associated with IR. This makes little sense to me, the main use seems to be to get correct offsets for different instructions in an IR sequence. Since block IR includes temp initialization bytes, the offset is 5. Changing the code to record *starting* offset of an IRNode in IRSequence, by: mapBytesTo: instr "Associate the current byte offset with instr. We fix this later to have the correct offset, see #bytecodes" instrMap add: instr -> (bytes size + 1) and mapping bytes *before* visiting node in the IRTranslatorV2: visitInstruction: instr gen mapBytesTo: instr. self visitNode: instr. and the same in visitPushClosureCopy: closure closure copiedValues do: [:name | gen mapBytesTo: closure. gen pushTemp: (self currentScope indexForVarNamed: name). ]. --snip-- Plus changing IRMethod >> instructionForPC: aPC to scan backwards to find the start of in-mid PC (for now up to 3 bytes): self compiledMethod. "generates the compiledMethod and optimize the ir. Removes the side-effect of optimizing the IR while looking for instruction, which results in incorrect found instruction" self haltOnce. 0 to: 3 do: [ :off | (self firstInstructionMatching: [:ir | ir bytecodeOffset = (aPC - off) ]) ifNotNil: [:it |^it]] We get more sensible results from the above tests for argumentNames/sourceNode. Amazingly, debugger range hilighting seems to keep working as well :) Cheers, Henry

Oct. 12, 2015

Re: [Pharo-dev] seg fault on Ubuntu when launching

by Robert Withers

I am brand new to Ubuntu, as well. I am pretty lost with versions. How would I check? I installed whatever came with apt-get. Oh, I tried a image/changes for the launcher dated 2015.09.14, if that helps. It segfaulted. - Robert On 10/12/2015 09:36 AM, phil(a)highoctane.be wrote: > I am using Ubuntu 14.04 and Pharo Launcher without issues. > > Which image ? 4.0? > > Phil > > On Mon, Oct 12, 2015 at 3:27 PM, Robert Withers > <robert.w.withers(a)gmail.com <mailto:robert.w.withers@gmail.com>> wrote: > > Hello, I am new to Pharo and just getting into it. > > I have Ubuntu and used PPA to install Pharo. The launcher is > failing with a segfault crash.dmp when trying to launch. It is the > UnixOSProcessAccessor>>forkAndExec... that is segaulting. I > looked in /usr/lib/pharo-vm and do not see a UnixOSProcess plugin. > Is it internal? > > I am able to launch an image from outside the launcher. > > -- > thanks, > Robert > > > -- thanks, Robert

Oct. 12, 2015

[ANN] Cupboard inspector for Teapot

by Torsten Bergmann

Hi, I took a few minutes to add a custom inspector tool ("Cupboard") to Teapot showing all the available teapots. The tool is accessible from the Tool menu right after loading "Teapot" and allows get an overview on running teapots. If you teapot has dynamic routes they will be shown as well. See screenshot attached. You can also start/stop a Teapot or add a new one serving static contents from a selected directory. Also catalog messages were added to the ConfigurationOfTeapot and the NeoJSON repo in the dependencies was fixed. Just get the lates stable version: Gofer it smalltalkhubUser: 'zeroflag' project: 'Teapot'; configuration; loadStable. or directly load from ConfigBrowser (Pharo 4) or CatalogBrowser/Spotter (Pharo 5) in a fresh image. If you want to quickly serve a (static) webpage from Pharo ========================================================== Create a web directory and HTML page - use "Tools" -> "File Browser" - create a directory "www" using "Add new directory", navigate to it - create a new file "index.html" using "Add new file", edit it and accept the changes Serve it from Pharo - load Teapot in a fresh image - open "Tools" -> "Teapot" - click on the server icon on the right to create a new static server - accept the default port 80 or enter a new one - select the directory Point your browser to http://localhost:80 If you want to quickly server (dynamic) content from Pharo: =========================================================== - use one of the examples on http://smalltalkhub.com/#!/~zeroflag/Teapot Note that the dynamic routes are shown in the new tool Tip: if you like use "Mustache" template library to mix HTML content (like Bootstrap templates, Material design templates or other with your Pharo server objects to serve pages) Have fun T.

Oct. 12, 2015

Re: [Pharo-dev] seg fault on Ubuntu when launching

by phil＠highoctane.be

I am using Ubuntu 14.04 and Pharo Launcher without issues. Which image ? 4.0? Phil On Mon, Oct 12, 2015 at 3:27 PM, Robert Withers <robert.w.withers(a)gmail.com> wrote: > Hello, I am new to Pharo and just getting into it. > > I have Ubuntu and used PPA to install Pharo. The launcher is failing with > a segfault crash.dmp when trying to launch. It is the > UnixOSProcessAccessor>>forkAndExec... that is segaulting. I looked in > /usr/lib/pharo-vm and do not see a UnixOSProcess plugin. Is it internal? > > I am able to launch an image from outside the launcher. > > -- > thanks, > Robert > > >

Oct. 12, 2015

Re: [Pharo-dev] hello

by phil＠highoctane.be

On Mon, Oct 12, 2015 at 3:20 PM, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > Hi SebastiÃ n, > > 2015-10-12 13:53 GMT+02:00 SebastiÃ¡n Krynski <skrynski(a)gmail.com>: > >> Hello my name is SebastiÃ¡n Krynski from Buenos Aires, Argentina. >> Just writing to let you know that I'm starting to work on adding an >> atomic swap operator in Pharo , guaranteed not to be interrupted by the VM. >> The operator will be used this way: >> >> a :=: b >> >> meaning 'swap variable a with variable b'. >> > > Why a cryptic, special syntax? The compiler could inline an explicit > message send which would make the intent clear. > See previous discussions about <=> indeed. > > a atomicSwapWith: b. > > Well, anyway, the compiler has to do something special there. > > Could we have something like... > > [ | temp | > temp := a. > a := b. > b := a ] atomic > > ? Would a compiler be able to merge that in a swap instruction? And make > another type of processing for a different code inside the block? > We have Mutex>>critical: aBlock etc. Why not Atomic>>do: aBlock ? Would indeed be more readable than :=: Phil > > >> In order to do this I will be modifying the VM and the Compiler . >> >> Good luck. This is an important step. > > >> I'm working under the direction of INRIA and Gabriela ArÃ©valo. >> > > Welcome! > > Thierry >

Oct. 12, 2015

seg fault on Ubuntu when launching

by Robert Withers

Hello, I am new to Pharo and just getting into it. I have Ubuntu and used PPA to install Pharo. The launcher is failing with a segfault crash.dmp when trying to launch. It is the UnixOSProcessAccessor>>forkAndExec... that is segaulting. I looked in /usr/lib/pharo-vm and do not see a UnixOSProcess plugin. Is it internal? I am able to launch an image from outside the launcher. -- thanks, Robert

Oct. 12, 2015

Re: [Pharo-dev] hello

by Thierry Goubier

Hi SebastiÃ n, 2015-10-12 13:53 GMT+02:00 SebastiÃ¡n Krynski <skrynski(a)gmail.com>: > Hello my name is SebastiÃ¡n Krynski from Buenos Aires, Argentina. > Just writing to let you know that I'm starting to work on adding an atomic > swap operator in Pharo , guaranteed not to be interrupted by the VM. The > operator will be used this way: > > a :=: b > > meaning 'swap variable a with variable b'. > Why a cryptic, special syntax? The compiler could inline an explicit message send which would make the intent clear. a atomicSwapWith: b. Well, anyway, the compiler has to do something special there. Could we have something like... [ | temp | temp := a. a := b. b := a ] atomic ? Would a compiler be able to merge that in a swap instruction? And make another type of processing for a different code inside the block? > In order to do this I will be modifying the VM and the Compiler . > > Good luck. This is an important step. > I'm working under the direction of INRIA and Gabriela ArÃ©valo. > Welcome! Thierry

Oct. 12, 2015

Re: [Pharo-dev] hello

by Max Leske

> On 12 Oct 2015, at 14:47, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > > Hello, > > If the operator is atomic that means if another thread (I am talking about native threads) interacts with the same portion of memory than the active thread its operation will be done after of before. This is a step toward a multithreaded VM with lock free algorithms and is different from just having a user interrupt or a process switch. #become: or the multiple assignments you showed are done in several cpu instructions hence another thread can manipulate the same memory while the operation is performed, which is not atomic. > > Hence, the way I understand it is that the operation :=: is done in 1 cpu instruction. SebastiÃ¡n has to change the bytecode compiler, the JIT and the interpreter to support that. That cannot be done with any variable, but it may be possible to implement :=: for at least 2 temporaries using the cpu swap. > > There is still a long way to go to have a multithreaded VM with lock-free algorithms, but one has to start somewhere I guess. I am not expert in concurrent programming but atomic swap or test and set operations are probably the way to go. I see. That does make sense. Thanks Clement. > > Cheers, > > Clement > > > > 2015-10-12 14:12 GMT+02:00 Max Leske <maxleske(a)gmail.com <mailto:maxleske@gmail.com>>: > >> On 12 Oct 2015, at 13:53, SebastiÃ¡n Krynski <skrynski(a)gmail.com <mailto:skrynski@gmail.com>> wrote: >> >> Hello my name is SebastiÃ¡n Krynski from Buenos Aires, Argentina. > > Hi SebastiÃ¡n, welcome! > >> Just writing to let you know that I'm starting to work on adding an atomic swap operator in Pharo , guaranteed not to be interrupted by the VM. The operator will be used this way: >> >> a :=: b >> >> meaning 'swap variable a with variable b'. >> In order to do this I will be modifying the VM and the Compiler . > > Sound cool! But isnât that the same as > > a become: b > > ? I even think that > > tmp := a. > a := b. > b := tmp > > is equivalent, since the VM only interrupts message sends, and in this case only byte code would be generated? > > Thatâs not my area of expertise, so please correct me. > > Cheers, > Max > >> >> I'm working under the direction of INRIA and Gabriela ArÃ©valo. >> > >

Oct. 12, 2015

Re: [Pharo-dev] hello

by ClÃ©ment Bera

Hello, If the operator is atomic that means if another thread (I am talking about native threads) interacts with the same portion of memory than the active thread its operation will be done after of before. This is a step toward a multithreaded VM with lock free algorithms and is different from just having a user interrupt or a process switch. #become: or the multiple assignments you showed are done in several cpu instructions hence another thread can manipulate the same memory while the operation is performed, which is not atomic. Hence, the way I understand it is that the operation :=: is done in 1 cpu instruction. SebastiÃ¡n has to change the bytecode compiler, the JIT and the interpreter to support that. That cannot be done with any variable, but it may be possible to implement :=: for at least 2 temporaries using the cpu swap. There is still a long way to go to have a multithreaded VM with lock-free algorithms, but one has to start somewhere I guess. I am not expert in concurrent programming but atomic swap or test and set operations are probably the way to go. Cheers, Clement 2015-10-12 14:12 GMT+02:00 Max Leske <maxleske(a)gmail.com>: > > On 12 Oct 2015, at 13:53, SebastiÃ¡n Krynski <skrynski(a)gmail.com> wrote: > > Hello my name is SebastiÃ¡n Krynski from Buenos Aires, Argentina. > > > Hi SebastiÃ¡n, welcome! > > Just writing to let you know that I'm starting to work on adding an atomic > swap operator in Pharo , guaranteed not to be interrupted by the VM. The > operator will be used this way: > > a :=: b > > meaning 'swap variable a with variable b'. > In order to do this I will be modifying the VM and the Compiler . > > > Sound cool! But isnât that the same as > > a become: b > > ? I even think that > > tmp := a. > a := b. > b := tmp > > is equivalent, since the VM only interrupts message sends, and in this > case only byte code would be generated? > > Thatâs not my area of expertise, so please correct me. > > Cheers, > Max > > > I'm working under the direction of INRIA and Gabriela ArÃ©valo. > > >

Oct. 12, 2015