Vm-dev April 2018

vm-dev@lists.squeakfoundation.org

43 participants
235 discussions

[OpenSmalltalk/opensmalltalk-vm] Improve {build.win32x86, build.win64x64}/HowToBuild to add description about cygwin dependencies (#237)
by CyrilFerlicot 19 Aug '18

19 Aug '18

See: http://forum.world.st/Compiling-the-windows-32-bits-vm-td5072691.html -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/237

2 1

Compiling the windows 32 bits vm
by Cyril Ferlicot D 12 Jul '18

12 Jul '18

Hello, I am trying to compile my first vm, so I read the README and HowToBuild on OpenSmalltalk git repository. I tried to build the build.win32x86/pharo.cog.spur flavour on Windows 7 after installing cygwin with this command: setup-x86.exe -dgnqNO -R "E:\cygwin" -s "http://cygwin.mirror.constant.com" -l "E:\cygwin\var\cache\setup" -P mingw64-i686-gcc-core,mingw64-i686-gcc-g++,mingw64-i686-headers,mingw64-i686-runtime,zip,mingw64-i686-clang,mingw64-i686-openssl,libiconv-devel,libglib2.0-devel,perl,mingw64-i686-zlib,make,cmake,wget,mingw64-i686-win-iconv The build fail with this error: config.status: creating config.h.win32 config.status: creating config.h config.status: executing depfiles commands config.status: executing libtool commands configure: WARNING: cache variable lt_cv_path_LD contains a newline make[2]: Entering directory '/cygdrive/e/cog/oscogvm/build.win32x86/pharo.cog.spur/builddbg/third-party/pkg-config-0.29.1' Makefile:311: *** missing separator. Stop. make[2]: Leaving directory '/cygdrive/e/cog/oscogvm/build.win32x86/pharo.cog.spur/builddbg/third-party/pkg-config-0.29.1' make[1]: *** [../third-party/Makefile.pkgconfig:26: /cygdrive/e/cog/oscogvm/.thirdparty-cache/windows/i386/bin/pkg-config.exe] Error 2 make[1]: Leaving directory '/cygdrive/e/cog/oscogvm/build.win32x86/pharo.cog.spur' make: *** [../common/Makefile:157: debug] Error 2 I have to say that I have really few experience with everything around the vm and maybe this is a problem easy to solve. But not with my knowledge. Does anyone has an idea of what might be the problem? Also, I'm not sure it is the right place for this kind of questions since it's vm-dev and this is a vm usage question. So, is it the right ML or is there another one? -- Cyril Ferlicot https://ferlicot.fr

7 20

SSL error on windows 7
by Cyril Ferlicot D 23 May '18

23 May '18

Hi Tobias, I have a problem with SSL and Winodws 7, I think it might be a VM plugin problem (excuse me if we find at the end that it is not) and I heard you're the one maintaining the SSL plugin. If I execute this code: ZnClient new url: 'https://google.com'; get. I get a result. If I execute this code: ZnClient new url: 'https://github.com'; get. I get this error: Error: SSL Exception: connect failed [code:-5] I tried with both stable and latest vm. (The stable is from august 2017 I think) I sent a mail on the Pharo dev ML and we are at least two having this problem with Windows 7 when it's working with Windows 10. Let me know if you need any more details on this issue. I opened on issue: https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/236 Here are the details and the stack: Image ----- E:\Pharo\images\Pharo 7.0 (development version)-22\Pharo 7.0 (development version)-22.image Pharo7.0alpha Build information: Pharo-7.0+alpha.build.749.sha.039a4b6f0d61ba99778349c4cff2c4e8d5ff9227 (32 Bit) Unnamed Virtual Machine --------------- C:\Users\JeCisC\Documents\Pharo\vms\70-x86\Pharo.exe CoInterpreter VMMaker.oscog-eem.2359 uuid: b3273e3e-dd9d-4819-a928-7034e1cf412c Mar 16 2018 StackToRegisterMappingCogit VMMaker.oscog-eem.2359 uuid: b3273e3e-dd9d-4819-a928-7034e1cf412c Mar 16 2018 VM: 201803161038 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Date: Fri Mar 16 11:38:09 2018 +0100 $ Plugins: 201803161038 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Win32 built on Mar 16 2018 11:02:19 GMT Compiler: 6.4.0 VMMaker versionString VM: 201803161038 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Date: Fri Mar 16 11:38:09 2018 +0100 $ Plugins: 201803161038 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ CoInterpreter VMMaker.oscog-eem.2359 uuid: b3273e3e-dd9d-4819-a928-7034e1cf412c Mar 16 2018 StackToRegisterMappingCogit VMMaker.oscog-eem.2359 uuid: b3273e3e-dd9d-4819-a928-7034e1cf412c Mar 16 2018 Operating System/Hardware ------------------------- Win32 6.1 IX86 Operating System Details ------------------------ Operating System: Windows 7 Professional N (Build 7601 Service Pack 1) SP major version: 1 SP minor version: 0 Suite mask: 100 Product type: 1 ============================================================== ZdcSecureSocketStream(Object)>>error: ZdcSecureSocketStream>>sslException:code: ZdcSecureSocketStream>>connect ZnClient>>setupTLSTo: ZnClient>>newConnectionTo: ZnClient>>getConnectionAndExecute ZnClient>>executeWithRedirectsRemaining: [ self executeWithRedirectsRemaining: self maxNumberOfRedirects ] in ZnClient>>executeWithRetriesRemaining: in Block: [ self executeWithRedirectsRemaining: self maxNumb...etc... BlockClosure>>on:do: ZnClient>>executeWithRetriesRemaining: [ self executeWithRetriesRemaining: self numberOfRetries ] in [ [ self executeWithRetriesRemaining: self numberOfRetries ] on: Error do: self ifFailBlock ] in ZnClient>>executeWithTimeout in Block: [ self executeWithRetriesRemaining: self numberOfR...etc... BlockClosure>>on:do: [ [ self executeWithRetriesRemaining: self numberOfRetries ] on: Error do: self ifFailBlock ] in ZnClient>>executeWithTimeout in Block: [ [ self executeWithRetriesRemaining: self numberO...etc... [ ^ block value ] in ZnClient>>withTimeoutDo: in Block: [ ^ block value ] [ activeProcess psValueAt: index put: anObject. aBlock value ] in ZnConnectionTimeout(DynamicVariable)>>value:during: in Block: [ activeProcess psValueAt: index put: anObject.... BlockClosure>>ensure: ZnConnectionTimeout(DynamicVariable)>>value:during: ZnConnectionTimeout class(DynamicVariable class)>>value:during: ZnClient>>withTimeoutDo: ZnClient>>executeWithTimeout [ result := self executeWithTimeout ] in ZnClient>>execute in Block: [ result := self executeWithTimeout ] [ ^ block value ] in ZnClient>>withProgressDo: in Block: [ ^ block value ] [ activeProcess psValueAt: index put: anObject. aBlock value ] in ZnSignalProgress(DynamicVariable)>>value:during: in Block: [ activeProcess psValueAt: index put: anObject.... BlockClosure>>ensure: ZnSignalProgress(DynamicVariable)>>value:during: ZnSignalProgress class(DynamicVariable class)>>value:during: ZnClient>>withProgressDo: ZnClient>>execute ZnClient>>get UndefinedObject>>DoIt -- Cyril Ferlicot https://ferlicot.fr

6 19

[OpenSmalltalk/opensmalltalk-vm] Add accurate check for console stdio + add associated primitive (#254)
by Vincent Blondeau 15 May '18

15 May '18

Related to https://github.com/pharo-project/pharo/pull/694 You can view, comment on, or merge this pull request online at: https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/254 -- Commit Summary -- * First Version * Improve Win API compatibility * Use the primitive in the main function * code ordering * move function to Win32Main + add stubs for other plateforms for the primitive implementation * remove useless imports -- File Changes -- M platforms/Cross/plugins/FilePlugin/FilePlugin.h (1) M platforms/Cross/plugins/FilePlugin/sqFilePluginBasicPrims.c (6) M platforms/RiscOS/plugins/FilePlugin/sqFilePluginBasicPrims.c (5) M platforms/win32/plugins/FilePlugin/sqWin32FilePrims.c (10) M platforms/win32/vm/sqWin32Main.c (112) M src/plugins/FilePlugin/FilePlugin.c (27) -- Patch Links -- https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/254.patch https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/254.diff -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/254

9 55

[OpenSmalltalk/opensmalltalk-vm] Boot images produced by 201801252341 VM don't bring up a window on launch (#196)
by Ryan Macnak 13 May '18

13 May '18

If I produce Newspeak [boot images](https://bitbucket.org/newspeaklanguage/nsboot) from the [201801252341 Mac VMs](https://github.com/OpenSmalltalk/opensmalltalk-vm/releases/tag/2018012…, these images do not bring up the UI when subsequently opened, either by the new VMs or old VMs. The new VMs are able to properly bring up images produced by old VMs. (Maybe there's some new headlessness property in the image header?) -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/196

3 6

Spur Memory segment and OS allocation
by Clément Bera 07 May '18

07 May '18

Hi Eliot, Hi all, On mac and linux, Spur uses mmap to allocate new segments. The V3 memory manager used malloc instead. I've looked into many other VMs (Javascript and Java), and most of them use posix_memalign (basically malloc where you can ask for specific alignment). I am wondering why we are using mmap over posix_memalign / malloc. The only reason I can find is that Spur always allocate new memory segments at a higher address than past segments to guarantee that young objects are on lower addresses than old objects for the write barrier. Is that correct? Assuming it is correct, let's say I change Spur to implement the write barrier differently (typically, I change all objects to be aligned on 128 bits instead of 64 and have different allocation alignment for young (128 bits alignment) and old objects(128+64 bits alignment)). Will we be able to use posix_memalign / malloc to allocate new memory segment if I do that ? Or does the VM rely on segments being on higher addresses for other reasons ? For example, does the VM assume CogMethods are on lower addresses than objects on heap and rely on it to check if a stack frame is mframe or iframe ? Thanks, -- Clément Béra https://clementbera.github.io/ https://clementbera.wordpress.com/

3 5

[OpenSmalltalk/opensmalltalk-vm] another try to properly build libgit2 (#253)
by Esteban Lorenzano 07 May '18

07 May '18

You can view, comment on, or merge this pull request online at: https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/253 -- Commit Summary -- * another try to properly build libgit2 -- File Changes -- M build.linux32x86/third-party/Makefile.libgit2 (8) -- Patch Links -- https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/253.patch https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/253.diff -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/253

1 13

StackInterp/Cog>>transferTo: - assertValidExecutionPointe:r:s differences
by Ben Coman 06 May '18

06 May '18

Just curious about the difference in instructionPointer between these two... StackInterpreter>>transferTo: self assertValidExecutionPointe: instructionPointer + 1 r: framePointer s: stackPointer. CoIntepreter>>transferTo:from: self assertValidExecutionPointe: instructionPointer r: framePointer s: stackPointer. cheers -ben

3 8

Understanding FFI type/spec
by Nicolas Cellier 29 Apr '18

29 Apr '18

I'm still struggling with FFI. And more specifically ExternalType and compiledSpec. The headerWord of the compiledSpec is composed of those bits: atomicTypeCode - atomic-pointer-struct bits - byteSize (4 bits used/8 high bits) - (3 bits used/8 bits) - (16 low bits) So, the atomic type short is encoded with atomicType=5, atomicBit(4),size=2: ExternalType short compiledSpec first hex -> '16r5040002' and short *, is same with pointerBit(2) set, and size=pointer size (4 on 32bits) ExternalType short asPointerType compiledSpec first hex -> '16r5060004' Note that I had to correct the pointer size for 64 bits in FFI-Kernel-nice.52!!! (I corrected the same bug in the plugin a few days back, so it's better to match). Now what happens with an ExternalStructure? it has the structureBit(1) set: (ExternalType structTypeNamed: #FFITestPoint2) compiledSpec first hex -> '16r10008' OK, and what about FFITestPoint2 *? (ExternalType structTypeNamed: #FFITestPoint2) asPointerType compiledSpec first hex -> '16r20004' Ah, surprising, it has the pointerBit(2) set, but no structureBit nor atomicBit. My own expectation would be 16r30004... So I thought that this could have been on purpose to match void *, but no: ExternalType void asPointerType compiledSpec first hex -> '16r60004' And what about type aliases? (ExternalType structTypeNamed: #Win32Handle) compiledSpec first hex -> '16r6040004' Since it is an alias for ulong (understand uint32_t), we get the same compiledSpec ExternalType ulong compiledSpec first hex -> '16r6040004' OK, and what about a Win32Handle* (if it ever makes sense) (ExternalType structTypeNamed: #Win32Handle) asPointerType compiledSpec first hex -> '16r20004' Ouch ! Doubly surprising, it's like any other structure! If I want to alias a type, is the pointer to the alias really going to work as expected??? ExternalType ulong asPointerType compiledSpec first hex -> '16r6060004' And now, let's insepct some code: isStructureType "Return true if the receiver represents a structure type" ^self headerWord anyMask: FFIFlagStructure isPointerType "Return true if the receiver represents a pointer type" ^self isStructureType not and:[self headerWord anyMask: FFIFlagPointer] embeddedSpecWithSize: typeSize "Return a compiled spec for embedding in a new compiled spec." | spec header | spec := self compiledSpec copy. header := spec at: 1. header := (header bitAnd: FFIStructSizeMask bitInvert32) bitOr: typeSize. spec at: 1 put: header. (self isStructureType and:[self isPointerType not]) ifTrue:[spec := spec copyWith: self class structureSpec]. ^spec I absolutely do not understand such code. 1- (self isStructureType and:[self isPointerType not]) is always false with the above definitions!!! 2- If it were not, I don't understand the intention to follow embedded structures (nested structures) specs with a void structure spec 16r10000, nor where it is used... And yet another obscure and questionable choice: alias to a pointer: compileAlias: spec withAccessors: aBool ...snip... isPointerField ifTrue:[compiledSpec := WordArray with: (ExternalType structureSpec bitOr: ExternalType pointerSpec)] ifFalse:[compiledSpec := externalType compiledSpec]. So finally, the combination pointerBit(2)+structureBit(1) is used in the system, not exactly where I expected, but when a type is an alias to a pointer (but remember, not necessarily a pointer to a structure). (ExternalType structTypeNamed: #MacPixPatPtr) compiledSpec first hex -> '16r30004' Completely brainfuck: the least I expect from such niceties is looonng and well detailed explanation. Where is the F... manual? With this ability of human brain to perceive order in perfectly random patterns, I'm just beginning to see the light: for some reasons, we want an alias to a pointer not being handled as a pointer, thus the special use case for pointerBit+structureBit (16r30004) and thus the bizarre definition of isPointerType... Now what are those reasons? I'm in a situation where I have plenty of very logical FFI declarations that just don't work. I thought I had understood enough of FFI to propose some corrections to the plugin. But now, I'm not even sure. And maintaining backward compatibility with obscure undocumented features is going to be very challenging... Sometimes, the Pharo style scorched earth policy is very tempting ;) Or I can just fork, implement the missing multiple-pointer-level spec, the missing array spec, the missing union spec, correct the 64bits slips, handle the alignment... Before inventing my own square wheel, I will have another look at Esteban's UFFI, he has been there before me. Nicolas

1 0

GC
by Eliot Miranda 27 Apr '18

27 Apr '18

Hi Clément, Hi All, I answered a question on Quora on GC recently and that same question was answered by Jon Harrop, who has taken a good look at GC performance. If you're not on Quora yet, let me encourage you. This blog post is a good read: https://flyingfrogblog.blogspot.co.uk/2017/12/does-reference-counting-reall… And in Jon's answer to the Quora question he mentions Staccato, A Parallel and Concurrent Real-time Compacting Garbage Collector for Multiprocessors https://pdfs.semanticscholar.org/9770/fc9baf0f2b6c7521f00958973657bf03337d.… That's my reading for today. _,,,^..^,,,_ (phone)

5 7

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

Vm-dev April 2018