Hi all, anybody knows how to get (and test) the 64bits version of the Pharo vm and image? |
VM here: http://bintray.com/estebanlm/pharo-vm/build#files/
Image here: http://files.pharo.org/get-files/60/pharo-64.zip this is still not official (that’s why is not in official place) so there are a couple of known problems: - version format is different, and that breaks some things in image that depends on it to know what happens - command line is different and probably you’ll need to play a bit with options (one or two dashes). - UFFI has some failing tests (but most of it works). I would appreciate some help to report and/or fix the emerging problems. cheers, Esteban
|
2016-10-28 11:56 GMT+02:00 Esteban Lorenzano <[hidden email]>: Thanks.
I'll make myself a Makefile for it and test; if I see it stable enough, I'll try to use it on a regular basis and report. Thierry
|
2016-10-28 12:29 GMT+02:00 Thierry Goubier <[hidden email]>:
Report: apart from the missing SSL support which makes loading complex stuff from github a bit painfull, it seems to be usable enough. OSProcess and GitFileTree work fine. Which means gitfiletree:// urls work, but not github:// urls. I loaded a large project (a compiler!) and saw no issues (apart from a freetype / wrong glyph issue?). All SmaCC tests are green on it, and my project tests were green as well. Thierry
|
I faced an issue that FFI calls fail with arguments of type size_t or the value that was passed to C function was completely wrong. For example you pass 1 but get 29834693165 Cheers, Alex On 28 October 2016 at 14:22, Thierry Goubier <[hidden email]> wrote:
|
In reply to this post by Thierry Goubier
I should work on this :) Esteban
|
does 64 bit means that we can now take full advantage of the memory of our system and not have to adhere to a specific limit ? Is that something the current build does or is it planned for future releases ? On Fri, Oct 28, 2016 at 4:19 PM Esteban Lorenzano <[hidden email]> wrote:
|
Le 28/10/16 à 16:59, Dimitris Chloupis
a écrit :
yes well probably the one of your OS :) This one.
|
awesome thank you guys On Fri, Oct 28, 2016 at 7:05 PM stepharo <[hidden email]> wrote:
|
In reply to this post by EstebanLM
Hi Esteban,
Le 28/10/2016 à 11:56, Esteban Lorenzano a écrit : > VM here: http://bintray.com/estebanlm/pharo-vm/build#files/ What is the difference between the various x86_64 versions? I chose the itimer one for my tests. The threaded one is the "run external calls in their own thread" vm? Thanks, Thierry |
In reply to this post by EstebanLM
OMG, this thing is for real:
A Pharo image using 20 GB virtual memory, about 6/7 GB for real on macOS Sierra, after playing around a bit allocating massive amounts of memory. Pharo in the above screenshot holds two 2 basic inspectors open on two different 1 GB byte arrays, after GC consuming about 2.2 GB. This is a game changer. Yeah ! 2 ** 30 timesRepeat: [ Transcript crShow: 'Thank you !' ]. On 28 Oct 2016, at 11:56, Esteban Lorenzano <[hidden email]> wrote: |
In reply to this post by Thierry Goubier
Hi Thierry,
On Fri, Oct 28, 2016 at 11:23 AM, Thierry Goubier <[hidden email]> wrote: Hi Esteban, No. The "threaded" one uses a separate thread for generating the heartbeat. The timer one uses a signal-based interval timer. You want the threaded one. The signal-based implementation causes havoc with external code. Thanks, _,,,^..^,,,_ best, Eliot |
^ this. but the threaded one requires a config on linux. (executing it by command line will point you to the correct NOTE, just s/squeak/pharo :) ) Esteban
|
In reply to this post by Eliot Miranda-2
Hi Eliot,
Le 29/10/2016 à 01:23, Eliot Miranda a écrit : > Hi Thierry, > > On Fri, Oct 28, 2016 at 11:23 AM, Thierry Goubier > <[hidden email] <mailto:[hidden email]>> wrote: > > Hi Esteban, > > Le 28/10/2016 à 11:56, Esteban Lorenzano a écrit : > > VM here: http://bintray.com/estebanlm/pharo-vm/build#files/ > <http://bintray.com/estebanlm/pharo-vm/build#files/> > > > What is the difference between the various x86_64 versions? I chose > the itimer one for my tests. The threaded one is the "run external > calls in their own thread" vm? > > > No. The "threaded" one uses a separate thread for generating the > heartbeat. The timer one uses a signal-based interval timer. You want > the threaded one. The signal-based implementation causes havoc with > external code. Thanks. I've also found the instructions for allowing the threaded one under Linux. Thierry |
In reply to this post by EstebanLM
Le 28/10/2016 à 15:18, Esteban Lorenzano a écrit :
> >> On 28 Oct 2016, at 14:22, Thierry Goubier <[hidden email] >> <mailto:[hidden email]>> wrote: >> >> apart from the missing SSL support which makes loading complex stuff >> from github a bit painfull, it seems to be usable enough. > > I should work on this :) Anything we can be of help on this? In the meantime, I'm becoming expert at writing wget requests to github to get tarballs of smalltalk projects :) Thierry > Esteban |
I cannot see the text I type into the Spotter’s search bar. Otherwise everything is great so far.
Uko > On 29 Oct 2016, at 17:09, Thierry Goubier <[hidden email]> wrote: > > Le 28/10/2016 à 15:18, Esteban Lorenzano a écrit : >> >>> On 28 Oct 2016, at 14:22, Thierry Goubier <[hidden email] >>> <mailto:[hidden email]>> wrote: >>> >>> apart from the missing SSL support which makes loading complex stuff >>> from github a bit painfull, it seems to be usable enough. >> >> I should work on this :) > > Anything we can be of help on this? > > In the meantime, I'm becoming expert at writing wget requests to github to get tarballs of smalltalk projects :) > > Thierry > >> Esteban > > |
And roassal is not working probably because of some Cairo bindings
> On 1 Nov 2016, at 10:39, Yuriy Tymchuk <[hidden email]> wrote: > > I cannot see the text I type into the Spotter’s search bar. Otherwise everything is great so far. > > Uko > >> On 29 Oct 2016, at 17:09, Thierry Goubier <[hidden email]> wrote: >> >> Le 28/10/2016 à 15:18, Esteban Lorenzano a écrit : >>> >>>> On 28 Oct 2016, at 14:22, Thierry Goubier <[hidden email] >>>> <mailto:[hidden email]>> wrote: >>>> >>>> apart from the missing SSL support which makes loading complex stuff >>>> from github a bit painfull, it seems to be usable enough. >>> >>> I should work on this :) >> >> Anything we can be of help on this? >> >> In the meantime, I'm becoming expert at writing wget requests to github to get tarballs of smalltalk projects :) >> >> Thierry >> >>> Esteban >> >> > > |
In reply to this post by EstebanLM
Hi Esteban, Another question about Pharo 64 bits. 2016-10-28 11:56 GMT+02:00 Esteban Lorenzano <[hidden email]>:
|
BTW, the threaded version requires to
be run as super user because it tries to do a
pthread_setschedparam(). I tried to fiddle with
/etc/security/limits.conf... but it's not something fancy to do...
Best regards, Casimiro Barreto Em 03-11-2016 13:53, Thierry Goubier escreveu:
--
The information contained in this message is confidential and intended to the recipients specified in the headers. If you received this message by error, notify the sender immediately. The unauthorized use, disclosure, copy or alteration of this message are strictly forbidden and subjected to civil and criminal sanctions. == This email may be signed using PGP key ID: 0x4134A417 signature.asc (876 bytes) Download Attachment |
no, is not hard. you just need to add this file: pharo.conf * hard rtprio 2 * soft rtprio 2 to: /etc/security/limits.d Esteban
|
Free forum by Nabble | Edit this page |