- Pharo-dev - lists.pharo.org

Nice library looking for clever developers for little chat and lovely documentation
by stepharong Feb. 12, 2017

Feb. 12, 2017

Hi guys I realized that value: valueWithPossibleArguments: cull: and others supernice messages do not have the method comments they deserved. cull: anArg ^numArgs = 0 ifTrue: [self value] ifFalse: [self value: anArg] => I started https://pharo.fogbugz.com/f/cases/19689/Add-method-comments-to-cool-block-m… cull: anArg "Execute the receiver with one or zero arguments depending on the receiver number of required arguments." "([ 12 ] cull: 13) >>> 12 " "([:x | x + 12] cull: 3) >>> 15 " ^numArgs = 0 ifTrue: [self value] ifFalse: [self value: anArg] Any takers? because it would be really nice to say to newcomers that our core libraries are super cool. Stef

1 0

Context stack semantics (was Re: GTDebugger variables table)
by Ben Coman Feb. 12, 2017

Feb. 12, 2017

On Fri, Feb 3, 2017 at 11:33 AM, Ben Coman <btc(a)openinworld.com> wrote: > > On Fri, Feb 3, 2017 at 10:21 AM, Ben Coman <btc(a)openinworld.com> wrote: >> >> Or maybe it [Stack] would be better as a tab of thisContext's next pane. >> > > Actually you can try this now... > > Context>>stackValueMap > | stackValues stackDepth| > stackValues := OrderedCollection new. > stackDepth := self basicSize min: 21. > (stackDepth to: 1 by: -1) do: [ :index | > |key| > key := (index = stackDepth) ifTrue: ['Top'] ifFalse: [(stackDepth - index + > 1) asString]. > stackValues add: (key -> (self basicAt: index)) > ]. > ^stackValues > > Context>>gtInspectorStackValuesIn: composite > <gtInspectorPresentationOrder: 40> > | stackValues | > stackValues := self stackValues. > ^ (composite table) > title: 'Stack'; > display: [ self stackValueMap ]; > column: 'Depth' evaluated: [ :assoc | assoc key ] width: 50; > column: 'Item' evaluated: [ :assoc | GTObjectPrinter new > asTruncatedTextFrom: assoc value ] > > > I'm not sure whether the #stackValueMap is an appropriate name. Perhaps it > should be #methodStackValueMap or something else? Similar for the tab name. A couple of times already I've missed not having this in fresh Images. Since its simple and low impact I hoping to add it for Pharo 6, but I'd like to check the semantics are right As a comparison, what I understand of C lang is it has only one stack (per thread) for: * execution flow return to caller's next statement * function parameters * function local variables So C kind of combines call stack and variable stack.. In Pharo, the top pane of the debugger shows a stack of Contexts as returned by "thisContext stack" which is effectively is for * execution flow return to caller's next statement And from what I learnt writing #stackValueMap above it seems , that each Context has its own stack for: * function parameters * function local variables * calculations / parameter marshalling for message sends So how should the second stack be referred to? Any of the following? * methodStackValues? * contextStackValues? * valueStack? * stackValues? and btw I wonder if Context>>stack would be better named Context>>callStack Here is my current refinement of the methods... Context>>stackValues | stackValues stackDepth| stackValues := OrderedCollection new. stackDepth := self basicSize min: 21. (stackDepth to: 1 by: -1) do: [ :index | stackValues add: (self basicAt: index) ]. ^stackValues Context>>composite <gtInspectorPresentationOrder: 30> |stackValues| stackValues := self stackValues. ^ composite table title: 'Value Stack'; display: [ :aCollection | [(1 to: stackValues size) collect: [ :index | index -> (stackValues at: index) ]] on:Error do:[#()]]; beMultiple; column: 'Index' evaluated: [ :assoc | (assoc key = 1 ifTrue: ['Top'] ifFalse: [ assoc key asString ])] width: 50; column: 'Item' evaluated: [ :assoc | GTObjectPrinter new asTruncatedTextFrom: assoc value ]; send: [ :result | result isNil ifTrue: [ nil ] ifFalse: [ result value size = 1 ifTrue: [result anyOne value] ifFalse: [self species withAll: (result collect: [:each | each value])]]]; showOnly: 50 cheers -ben

1 0

Re: [Pharo-dev] Segmentation fault while installing Scale
by Andrey Tykhonov Feb. 11, 2017

Feb. 11, 2017

Hi all, I've managed to get all information from the System report browser. I'll attach it to this email. Surprisingly (at least for me), Pharo doesn't crash if I execute it like the following: strace -f ./pharo-ui Pharo.image (before this, I executed it without -f). So, I'm attaching also part of the output from the command execution. strace generates a lot of such log messages like you can see in the log file strace-f-pharo.log (something is wrong, but I'm not sure what exactly is wrong). Best regards, Andriy.

1 0

[pharo-project/pharo-core] fcd75f: 60386
by GitHub Feb. 11, 2017

Feb. 11, 2017

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: fcd75f0830aa6925f2fee68011ae20fb30efee81 https://github.com/pharo-project/pharo-core/commit/fcd75f0830aa6925f2fee680… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2017-02-11 (Sat, 11 Feb 2017) Changed paths: R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60385.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60386.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60385.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60386.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Tool-FileList.package/FileList.class/instance/accessing/contents.st A Tool-FileList.package/FileList.class/instance/accessing/getEncoding.st M Tool-FileList.package/FileList.class/instance/file menu action/getHex.st A Tool-FileList.package/FileList.class/instance/private/knownEncodingIdentifiers.st M Tool-FileList.package/FileList.class/instance/private/readContentsBrief_.st M Tool-FileList.package/FileList.class/instance/private/readContentsHex_.st M Tool-FileList.package/FileList.class/instance/private/selectEncoding.st A Tool-FileList.package/FileList.class/instance/private/streamFirst5000BytesFrom_.st A Tool-FileList.package/FileList.class/instance/private/streamFirst5000BytesWithEncodingFrom_.st A Tool-FileList.package/FileList.class/instance/private/streamFullContentsFrom_.st A Tool-FileList.package/FileList.class/instance/private/streamFullContentsWithEncodingFrom_.st Log Message: ----------- 60386 18778 FileList "View as" does not work https://pharo.fogbugz.com/f/cases/18778 http://files.pharo.org/image/60/60386.zip

2 1

[pharo-project/pharo-core]
by GitHub Feb. 11, 2017

Feb. 11, 2017

Branch: refs/tags/60386 Home: https://github.com/pharo-project/pharo-core

1 0

Pharo 60 need help on When-coding-in-the-debugger-I-get-an-error-sourceNodeExecuted
by Stephane Ducasse Feb. 10, 2017

Feb. 10, 2017

https://pharo.fogbugz.com/f/cases/19661/When-coding-in-the-debugger-I-get-a… Then I got a really strange problem when I was doing the counter execise using the debugger. create a Test Case TestCase subclass: #CounterTest instanceVariableNames: '' classVariableNames: '' package: 'Counter' - add testValueAtCreation self assert: (Counter new count: 10) count equals: 10 - ok to define classes - define count: in the class Counter - count: anInteger count := anInteger - Declare instance variable count NOW problem Instance of class did not understand count - ok to define it => Instance of IRMethod do not understand sourceNodeExecuted HAnging around instances ========== Then if I remove the Counter class and relaunch the tests I get Instance of anObsoleteCounter did not understandâ¦.

3 2

Re: [Pharo-dev] Segmentation fault while installing Scale
by Andrey Tykhonov Feb. 10, 2017

Feb. 10, 2017

Hello, > Hi, > We are looking at it with Santi. I see in the log that you're using an ubuntu 12? No, this is Gentoo Linux. > I tried in a debian jessie and Santi in an ubuntu 14 and we could not > reproduce it. Also the travis ci of scale uses ubuntu 12 and the > installation works in there... > Could you give more details about your system? Sure, but I'm not sure which exactly information will be useful, so, please clarify. For now, I'm sending you kernel version: $ uname -a Linux tp 4.9.6-gentoo #1 SMP Thu Jan 26 17:04:47 EET 2017 x86_64 Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz GenuineIntel GNU/Linux > Thanks, Guille and Santi Thank you! -- Andriy

1 0

Re: [Pharo-dev] Segmentation fault while installing Scale
by Andrey Tykhonov Feb. 10, 2017

Feb. 10, 2017

Hi Clement, > Hi Andrey, > Thanks for providing both a way to reproduce and the log so we can have you > machine details. I see that the VM was compiled from build #589 on jenkins > with VMMaker.oscog-eem.1855 and you're on Linux using x86 back-end. > Scale works only on Linux and when I try the wget command from Mac it does > not work so I can't reproduce right now. > I suggest that for now you try to use one of the newer VMs (from > http://files.pharo.org/vm/pharo-spur32/linux/ , you're > using stable-20160504.zip, pick another one, It seems, the latest VM is downloaded. It is downloaded by means of the following command: wget -O - get.pharo.org/50+vm | bash Does it download old VM. Is this script outdated? I suggest a more recent one > than from May last year, either stable-20160623.zip > or pharo-linux-i386itimer-201702061308-aa78f27.zip) and then use the > "classic installation" to be able to use another VM than the one downloaded > by the wget script until someone can have a look into your problem. Could you please help, where could I get Pharo.image file which is required to execute pharo/pharo-ui? If I use existing one (with a VM taken from either stable-20160623.zip or pharo-linux-i386itimer-201702061308-aa78f27.zip), the VM crashes. So, it seems, I need another Pharo.image as well, right? With the best regards, Andriy

1 0

Re: [Pharo-dev] Segmentation fault while installing Scale
by Andrey Tykhonov Feb. 10, 2017

Feb. 10, 2017

Hi stephane > can you tell us on which OS and version This is Gentoo Linux. There is no such a thing like a version. There are kernel and a lot of software. Kernel version: # uname -a Linux tp 4.9.6-gentoo #1 SMP Thu Jan 26 17:04:47 EET 2017 x86_64 Intel(R) Core(TM) i7-6700HQ CPU @ 2 I found crash.dmp near pharo-ui,.60GHz GenuineIntel GNU/Linux Let me know please if I could provide more info on this matter. > and which VM do you use (there is a System report browser where you can find the information. It is downloaded by means of the command: wget -O - get.pharo.org/50+vm | bash AFAIU, the latest VM is downloaded by means of this command. I opened pharo-ui: ./pharo-ui Pharo.image > pharo.log and it was opened for a while, but it crashed when I tried to get information from System report browser. After that, I cannot open pharo-ui anymore. Two log files are attached to this email. Best regards, Andriy

1 0

Feb. 10, 2017

Hi, This is a lovely post. Thanks for posting about Smalltalk / Pharo / Squeak. 1. Why *exactly* does the override work (in 32bit images)? 2. What changed so that things are different in Squeak 5.1 64bit image (overrides partially work)? If I am correct your questions are exclusively for bitOr: and bitAnd:. I don't know what you are aware of and what you're not aware of, hence I am going to give you some details on how bitAnd: is executed (bitOr: is done exactly the same way), and hopefully there will be something you don't know yet that should help you understand what's going on. *Execution of bitAnd:* bitAnd: a special selector. If you run Smalltalk specialSelectors you get this array: #(#+ 1 #- 1 #< 1 #> 1 #<= 1 #>= 1 #= 1 #~= 1 #* 1 #/ 1 #\\ 1 #@ 1 #bitShift: 1 #// 1 #bitAnd: 1 #bitOr: 1 #at: 1 #at:put: 2 #size 0 #next 0 #nextPut: 1 #atEnd 0 #== 1 #class 0 #blockCopy: 1 #value 0 #value: 1 #do: 1 #new 0 #new: 1 #x 0 #y 0) which includes bitAnd: . Special selectors are encoded in the bytecode differently to save memory, so they can be executed differently without inducing overhead. In Cog, bitAnd: is executed differently using type-prediction. In the Stack Interpreter, the execution of bitAnd: is done as follows: If both operands are SmallIntegers, push the bitAnd: value of the 2 SmallIntegers else Try the primitive BitAnd for SmallIntegers (14) on success push the result on failure perform the send. In the JIT, bitAnd: sends are compiled differently that normal send, the compilation logic is as follows: If both operands are SmallInteger literals compute the result during compilation and use this value else If one of the 2 operands is a SmallInteger literal generate 2 paths, a quick inlined path testing at runtime that the other operand is a SmallInteger, and if so, Ands the operands and use that result, else use the slow path performing a send else generate a normal send *Primitives* primitive 14 -> Works for SmallIntegers and LargePositiveInteger fitting in an unsigned machine word. (Slower than direct SmallInteger bitAnd performed by the special selector) primitive 34 -> Works for SmallIntegers and LargePositiveInteger fitting in an unsigned int64. (Slower than primitive 14 in 32 bits but covering more cases, equivalent in 64 bits) primDigitBitAnd (in Integer) -> Works for any integer. (Slower than the primitive 14 and 34) *SmallInteger encoding* In 32 bits, SmallIntegers are signed 31bits integer. In 64 bits, SmallIntegers are signed 61 bits integer. *Discussion* Let's make some assertions based on previous information: 1) If you have the exact same bitAnd: implementation for #bitAnd: and #bitAnd2:, #bitAnd2: is slower because it is not a special selector. 2) Still with the exact same bitAnd: implementation, using the JIT, things like that: 16r1 bitAnd: 1. "1 bits" 16r2 bitAnd: 2. "2 bit" 16r4 bitAnd: 4. "3 bit" 16r8 bitAnd: 3. "4 bit" Are bitAnd: operations between SmallInteger constants and the result is unused. Hence this whole portion of code does not generate any native instructions. On the other hand, things like that: 16r1 bitAnd2: 1. "1 bits" 16r2 bitAnd2: 2. "2 bit" 16r4 bitAnd2: 4. "3 bit" 16r8 bitAnd2: 3. "4 bit" Are sends, generating multiple native instructions including calls. 3) Because of the SmallInteger encoding, 16r200000000000000 bitAnd: 98490667780264321. "58 bit" is compiled by the JIT to nothing in 64 bits but to a send in 32 bits (the JIT can't solve LargeInteger arithmetic at compilation time). 4) primitive 34 provides some speed-up over primitive 14 in 32 bits, covering bitAnd: operations from unsigned 33 bits integer to unsigned 64 bits integer, but makes no difference in 64 bits. In 64bits all the cases covered by primitive 34 are covered by primitive 14, so it should even slow down things. *So...* Does this answer your questions ? Don't hesitate to ask further questions. If you want more details, I wrote something about special selectors a while ago: https://clementbera.wordpress.com/2014/08/12/arithmetic-inlined-and-special… . Best, Clement PS1: If I'm correct, you referenced my blog a couple times, thank you for doing this, I really appreciate that. PS2: I enjoy chess myself, so if you have an open-source/MIT working algorithm at some point please send it to me, I will play against the AI and look at the code. On Fri, Feb 10, 2017 at 8:18 AM, Benoit St-Jean via Pharo-dev < pharo-dev(a)lists.pharo.org> wrote: > > > ---------- Forwarded message ---------- > From: Benoit St-Jean <bstjean(a)yahoo.com> > To: The General-purpose Squeak Developers List <squeak-dev@lists. > squeakfoundation.org>, "pharo-dev(a)lists.pharo.org" < > pharo-dev(a)lists.pharo.org> > Cc: > Date: Fri, 10 Feb 2017 07:18:02 +0000 (UTC) > Subject: Integer arithmetic and bit counting performance in Squeak and > Pharo > For those interested in performance of bit operations and integer > arithmetic in Squeak and Pharo : > > Bit operations in general : https://endormitoire.wordpress > .com/2017/02/10/bits-and-pieces/ > > Bit counting algorithms : https://endormitoire.wordpress > .com/2017/02/10/1001001-sos/ > > Some questions, some results, some answers... > > ----------------- > BenoÃ®t St-Jean > Yahoo! Messenger: bstjean > Twitter: @BenLeChialeux > Pinterest: benoitstjean > Instagram: Chef_Benito > IRC: lamneth > Blogue: endormitoire.wordpress.com > "A standpoint is an intellectual horizon of radius zero". (A. Einstein) > >

2 2