January 2017 - Pharo-dev - lists.pharo.org

Support for LP64 & LLP64 in FFI Kernel

by Eliot Miranda

Hi All, currently the FFI has support for 8, 16, 32 & 64 bit integers, but no support for C's long type. In almost all C implementations byte is 8 bits, short is 16 bits, int is 32 bits and long long is 64 bits. But long may be either 32 or 64 bits depending on programming model. In LP32 long is 32 bits, which is used in 32-bit unix, mac os and windows. In LP64 long is 64 bits, which is used in 64-bit unix and mac os. In LLP64 long is 32 bits, which is used in 64-bit windows. So having a type which is either 32 or 64 bits depending on platform is useful in modeling C's long type across platforms. Esteban and I propose adding such a type to FFI kernel, actually two types, one unsigned, one signed. So we propose extending the below (these constants are used to define signatures for FFI calls and the contents of structs) FFIConstants class>>#initializeTypeConstants "type void" FFITypeVoid := 0. "type bool" FFITypeBool := 1. "basic integer types. note: (integerType anyMask: 1) = integerType isSigned" FFITypeUnsignedByte := 2. FFITypeSignedByte := 3. FFITypeUnsignedShort := 4. FFITypeSignedShort := 5. FFITypeUnsignedInt := 6. FFITypeSignedInt := 7. "64bit types" FFITypeUnsignedLongLong := 8. FFITypeSignedLongLong := 9. "special integer types" FFITypeUnsignedChar := 10. FFITypeSignedChar := 11. "float types" FFITypeSingleFloat := 12. FFITypeDoubleFloat := 13. "type flags" FFIFlagAtomic := 16r40000. "type is atomic" FFIFlagPointer := 16r20000. "type is pointer to base type" FFIFlagStructure := 16r10000. "baseType is structure of 64k length" FFIStructSizeMask := 16rFFFF. "mask for max size of structure" FFIAtomicTypeMask := 16r0F000000. "mask for atomic type spec" FFIAtomicTypeShift := 24. "shift for atomic type" to add to "special integer types" FFITypeUnsignedChar := 10. FFITypeSignedChar := 11. FFITypePlatformUnsignedLong := 14. FFITypePlatformSignedLong := 15. This is backward compatible, even if it complicates the marshaling a little since it used to be that all integer types were less than FFITypeSingleFloat. But breaking backward compatibility would be a bad idea. Then in ByteArray et al we could add accessors for platformLongAt: platformUnsignedLongAt:. Comments, thoughts, objections? _,,,^..^,,,_ best, Eliot

Jan. 19, 2017

In the need of Pharo magic

by Stephane Ducasse

I would love to get a functionality that dynamically removes from my code all the self halt that are encountered during test execution. This way I will not need to run the test, walk the stack, edit the code and retart the process. It would be really cool

Jan. 19, 2017

Re: [Pharo-dev] genJumpLong: distance index 1043 is out of range -1024 to 1023

by Davide Varvello

Thanks guys, The forum.world.st didn't send me your replies and only now I'm aware of your replies. Thanks again Davide ClÃ©ment Bera-4 wrote > Hi, > > This will be fixed by using the alternative bytecode set, likely in the > next few weeks in Pharo 6 alpha/beta. Basically control flow messages > (ifTrue:, to:do:, etc.) cannot have too many statements in their blocks > (ifTrue: argument, to:do: second arguments, etc) or the compiler can't > compile them due to bytecode set encoding limitation. The new bytecode set > is encoded differently and allows such code to be compiled. > > As a temporary solution, you need to split your code in multiple methods > to > lower the number of statements inside blocks inside control flow messages. > > Sorry for the annoyance. We're working on integrating a solution and we > believe that this will be integrated in Pharo 6 in the next few weeks. > > Regards, > > Clement > > On Wed, Dec 7, 2016 at 4:14 PM, Davide Varvello via Pharo-dev < > pharo-dev@.pharo >> wrote: > >> >> >> ---------- Forwarded message ---------- >> From: Davide Varvello < > varvello@ > > >> To: > pharo-dev@.pharo >> Cc: >> Date: Wed, 7 Dec 2016 07:14:35 -0800 (PST) >> Subject: genJumpLong: distance index 1043 is out of range -1024 to 1023 >> Hi, >> >> Sometimes (and also today) after formatting and saving a method, an Error >> is >> thrown. >> Following a chunk of PharoDebug.log >> >> TIA >> Davide >> >> >> --------------------- >> THERE_BE_DRAGONS_HERE >> Error: genJumpLong: distance index 1043 is out of range -1024 to 1023 >> 7 December 2016 4:21:53.0426 pm >> >> VM: Mac OS - intel - 1096 - CoInterpreter >> VMMaker.oscog-HolgerHansPeterFreyther.1880 uuid: >> 16138eb3-2390-40f5-a6c8-15f0494936f8 Sep 30 2016 >> StackToRegisterMappingCogit VMMaker.oscog-HolgerHansPeterFreyther.1880 >> uuid: >> 16138eb3-2390-40f5-a6c8-15f0494936f8 Sep 30 2016 >> https://github.com/pharo-project/pharo-vm.git Commit: >> 06744effac0f0aa3b4b32e17636448f9d51d6707 Date: 2016-09-30 08:40:43 +0200 >> By: >> GitHub < > noreply@ > > Jenkins build #603 >> >> Image: Pharo5.0 [Latest update: #50763] >> >> OpalEncoderForV3PlusClosures(Object)>>error: >> Receiver: an OpalEncoderForV3PlusClosures >> Arguments and temporary variables: >> aString: 'genJumpLong: distance index 1043 is out >> of range -1024 to 1023' >> Receiver's instance variables: >> stream: an IRBytecodeGenerator >> position: nil >> rootNode: nil >> blockExtentsToLocals: nil >> >> >> OpalEncoderForV3PlusClosures(OpalBytecodeEncoder)>> >> outOfRangeError:index:range:to: >> Receiver: an OpalEncoderForV3PlusClosures >> Arguments and temporary variables: >> string: 'distance' >> index: 1043 >> rangeStart: -1024 >> rangeEnd: 1023 >> Receiver's instance variables: >> stream: an IRBytecodeGenerator >> position: nil >> rootNode: nil >> blockExtentsToLocals: nil >> >> >> OpalEncoderForV3PlusClosures(OpalEncoderForV3)>>genJumpLong: >> Receiver: an OpalEncoderForV3PlusClosures >> Arguments and temporary variables: >> distance: 1043 >> Receiver's instance variables: >> stream: an IRBytecodeGenerator >> position: nil >> rootNode: nil >> blockExtentsToLocals: nil >> >> >> OpalEncoderForV3PlusClosures(OpalEncoderForV3)>>genJump: >> Receiver: an OpalEncoderForV3PlusClosures >> Arguments and temporary variables: >> distance: 1043 >> Receiver's instance variables: >> stream: an IRBytecodeGenerator >> position: nil >> rootNode: nil >> blockExtentsToLocals: nil >> >> >> >> -- >> View this message in context: http://forum.world.st/ >> genJumpLong-distance-index-1043-is-out-of-range-1024-to- >> 1023-tp4926103.html >> Sent from the Pharo Smalltalk Developers mailing list archive at >> Nabble.com. >> >> >> -- View this message in context: http://forum.world.st/genJumpLong-distance-index-1043-is-out-of-range-1024-… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Jan. 19, 2017

AioPlugin not present

by Davide Varvello

Hi Folks, Actually It seems on the linux vm the AioPlugin isn't included. I worked on old vm, but I also downloaded the latest vm http://files.pharo.org/vm/pharo-spur32/linux/latest.zip and the result is the same. See the screenshot here http://imgur.com/a/9jhMy How can I add the plugin? TIA Davide -- View this message in context: http://forum.world.st/AioPlugin-not-present-tp4929932.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Jan. 19, 2017

Re: [Pharo-dev] looking for classbuilder API

by denker

There is #newAnonymousSubclass for creating a subclass from the current class. It seems that this is what this code is trying to do. Marcus > On 15 Jan 2017, at 09:40, stepharong <stepharong(a)free.fr> wrote: > > HI > > I need to migrate > > pvtNewSubclass > > | newClass | > newClass := Behavior new. > newClass superclass: self. > newClass setFormat: (ClassBuilder new computeFormat: #normal instSize: 0 forSuper: self ccIndex: 0). > ^newClass > > and I'm looking at how to express (ClassBuilder new computeFormat: #normal instSize: 0 forSuper: self ccIndex: 0). in Pharo 60. > > Stef >

Jan. 19, 2017

Re: [Pharo-dev] looking for classbuilder API

by Stephane Ducasse

tx I will try. On Sun, Jan 15, 2017 at 10:38 AM, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > maybe : > > newClass setFormat: self classLayout format. > > > 2017-01-15 9:40 GMT+01:00 stepharong <stepharong(a)free.fr>: > >> HI >> >> I need to migrate >> >> pvtNewSubclass >> >> | newClass | >> newClass := Behavior new. >> newClass superclass: self. >> newClass setFormat: (ClassBuilder new computeFormat: #normal >> instSize: 0 forSuper: self ccIndex: 0). >> ^newClass >> >> and I'm looking at how to express (ClassBuilder new computeFormat: >> #normal instSize: 0 forSuper: self ccIndex: 0). in Pharo 60. >> >> Stef >> >> >

Jan. 19, 2017

Re: [Pharo-dev] ***Important*** Snapcraft pharo package for Pharo 50

by Esteban Lorenzano

> On 18 Jan 2017, at 13:47, Holger Freyther <holger(a)freyther.de> wrote: > > >> On 6 Jan 2017, at 15:07, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Hi! > > >> looks same idea of http://openbuildservice.org, I hope this is easier (I never understood how to make OBS work for usâ¦ never had the time either :( ) > > The pharo-vm git repository gained creating a debian source package and I added auto-upload of it to OBS from travis-ci, with some extra packages (libsdl2) the same can be done for Ubuntu and one could create RPM .spec files (one to target multipke distributions). > > What is the current state of the Opensmalltalk-vm merge? It seems to be in progress and there some stability issues (e.g. unit tests are currently disabled)? > > Once the merge is done, tests are ran, I am happy to help using OBS to create packages for various Linux distributions. wowâ¦ this is super good, Holger, I want this since ages ! merge is done. there are 5 failing tests (and I still do not configure the tests for 64bits)â¦ I will work a bit on this this week, but Iâm finishing 3 things at the same time now (FFI 64bits, iceberg multi-remotes and this) so it will arriveâ¦ anytime soon. I wouldnât wait until the tests are running :) cheers! Esteban > > cheers > holger

Jan. 18, 2017

Re: [Pharo-dev] ***Important*** Snapcraft pharo package for Pharo 50

by Holger Freyther

> On 6 Jan 2017, at 15:07, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: Hi! > looks same idea of http://openbuildservice.org, I hope this is easier (I never understood how to make OBS work for usâ¦ never had the time either :( ) The pharo-vm git repository gained creating a debian source package and I added auto-upload of it to OBS from travis-ci, with some extra packages (libsdl2) the same can be done for Ubuntu and one could create RPM .spec files (one to target multipke distributions). What is the current state of the Opensmalltalk-vm merge? It seems to be in progress and there some stability issues (e.g. unit tests are currently disabled)? Once the merge is done, tests are ran, I am happy to help using OBS to create packages for various Linux distributions. cheers holger

Jan. 18, 2017

Re: [Pharo-dev] [ANN] Snapcraft for Pharo

by Guillermo Polito

No problem ;) BTW, you can find latest `already package` snaps in bintray here: https://bintray.com/pharo-project/pharo/PharoVM-Snap (Also the readme is updated) Guille On Wed, Jan 18, 2017 at 10:28 AM, Alistair Grant <akgrant0710(a)gmail.com> wrote: > On 17 January 2017 at 00:40, Guillermo Polito <guillermopolito(a)gmail.com> > wrote: > > Hi all, > > ... > > > > Alistair, > > - thanks for the typo. Maybe we can force wget as a build dependency? > Like > > that it will not fail like that ;) > > - I'll fix the typos. However, next time could you just open a pull > > request? or make an issue? emails tend to get lost (specially in a > weekend > > and with many answers :P) > > Sure, I'll create the pull request next time (I was a bit distracted > and didn't even think of it :-(). > > Thanks again, > Alistair > >

Jan. 18, 2017

Re: [Pharo-dev] [ANN] Snapcraft for Pharo

by Alistair Grant

On 17 January 2017 at 00:40, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > Hi all, > ... > > Alistair, > - thanks for the typo. Maybe we can force wget as a build dependency? Like > that it will not fail like that ;) > - I'll fix the typos. However, next time could you just open a pull > request? or make an issue? emails tend to get lost (specially in a weekend > and with many answers :P) Sure, I'll create the pull request next time (I was a bit distracted and didn't even think of it :-(). Thanks again, Alistair

Jan. 18, 2017