— |
@timfel @eliotmiranda Is there any specific reason not to have read-only primitive on ARM ? Where they not working ? — |
In reply to this post by David T Lewis
build.linux32ARMv[67]/pharo.cog.spur/build*/mvm is lacking -DIMMUTABILITY. c.f. -DIMMUTABILITY=1 in build.win*/pharo.cog.spur/Makefile build.macos*pharo.cog.spur/Makefile. I wish someone would volunteer to rewrite the linux build system to copy the much nicer scheme used in Mac OS and Windows. — |
In reply to this post by David T Lewis
I can't remember, but it should be fairly easy to try this out on our CI if you enable them on a branch. — |
In reply to this post by David T Lewis
So you're saying it's just a compilation setting but read-only objects work on ARM. Ok I'll enable them then. — |
In reply to this post by David T Lewis
@clementbera I didn't say they work on ARM, they may work. But please go ahead and try that out :) — |
In reply to this post by David T Lewis
Closed #216. — |
In reply to this post by David T Lewis
So that's solved and integrated. — |
In reply to this post by David T Lewis
Cool, thanks! — |
Where to get VM binary to test? Last binaries on bintray are from 12 days ago. And I checked latest Pharo VM for ARM. It returns false for "Smalltalk vm supportsWriteBarrier" 2018-03-17 17:46 GMT+01:00 Fabio Niephaus <[hidden email]>:
|
In reply to this post by David T Lewis
On Mon, Mar 19, 2018 at 3:02 PM, OpenSmalltalk-Bot <[hidden email] > wrote: > Where to get VM binary to test? > Last binaries on bintray are from 12 days ago. > And I checked latest Pharo VM for ARM. It returns false for "Smalltalk vm > supportsWriteBarrier" Hi Denis, Latest here: http://files.pharo.org/vm/pharo-spur32/linux/armv6/ should work. Seems bintray has been disabled for two weeks (invalid certificate to upload artifacts) > > > 2018-03-17 17:46 GMT+01:00 Fabio Niephaus <[hidden email]>: > > > > > > > Cool, thanks! > > > > — > > You are receiving this because you are subscribed to this thread. > > Reply to this email directly, view it on GitHub > > <https://github.com/OpenSmalltalk/opensmalltalk- > vm/issues/216#issuecomment-373934623>, > > or mute the thread > > <https://github.com/notifications/unsubscribe-auth/ > AhLyW0Mxb7XIun8HVIyzxqbn6SlmYohzks5tfT35gaJpZM4SFWOT> > > . > > > > > > > — > You are receiving this because you modified the open/close state. > Reply to this email directly, view it on GitHub > <https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/216#issuecomment-374222193>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AC0GgvDTsP1ni3FW_IRxZpeaenNuw00iks5tf7qIgaJpZM4SFWOT> > . > -- Clément Béra https://clementbera.github.io/ https://clementbera.wordpress.com/ — |
In reply to this post by David T Lewis
Hi Clement. CoInterpreter VMMaker.oscog-eem.2347 uuid: 062614a7-e3da-4b30-997a-9568911b9ff5 Mar 16 2018 Looks like it was build with version from 15 March. — |
In reply to this post by David T Lewis
8d716d4 uses a different Bintray user for deployments. Unfortunately, I cannot tell if this fixes the problem because the — |
In reply to this post by David T Lewis
Hi. Now we finally have new VMs. And write barrier properly works on Raspberry. All related tests are green in Pharo. Good job! Best regards, Denis 2018-03-19 15:52 GMT+01:00 Denis Kudriashov <[hidden email]>:
|
Free forum by Nabble | Edit this page |