[Pharo-dev] [Vm-dev] Re: Status of Pharo VM for FreeBSD
Andreas Wacknitz
A.Wacknitz at gmx.de
Fri Apr 3 15:14:32 UTC 2015
Am 03.04.15 17:04, schrieb Eliot Miranda:
>
>
>
> Hi Andreas,
>
> On Apr 3, 2015, at 4:04 AM, Andreas Wacknitz <A.Wacknitz at gmx.de
> <mailto:A.Wacknitz at gmx.de>> wrote:
>
>>
>> Am 03.04.15 11:13, schrieb Esteban Lorenzano:
>>>
>>>> On 02 Apr 2015, at 19:20, Eliot Miranda <eliot.miranda at gmail.com
>>>> <mailto:eliot.miranda at gmail.com>> wrote:
>>>>
>>>> Hi Andreas,
>>>>
>>>> sorry to be late in replying. This has been a busy month (I
>>>> moved house).
>>>>
>>>> On Sat, Mar 14, 2015 at 10:33 AM, Andreas Wacknitz
>>>> <a.wacknitz at gmx.de <mailto:a.wacknitz at gmx.de>> wrote:
>>>>
>>>>
>>>> Hi Eliot,
>>>>
>>>>> Am 11.03.2015 um 23:15 schrieb Eliot Miranda
>>>>> <eliot.miranda at gmail.com <mailto:eliot.miranda at gmail.com>>:
>>>>>
>>>>> HI Andreas,
>>>>>
>>>>> On Wed, Mar 11, 2015 at 9:55 AM, Andreas Wacknitz
>>>>> <a.wacknitz at gmx.de <mailto:a.wacknitz at gmx.de>> wrote:
>>>>>
>>>>>
>>>>> Hi Clement,
>>>>>
>>>>>> Am 11.03.2015 um 09:23 schrieb Clément Bera
>>>>>> <bera.clement at gmail.com <mailto:bera.clement at gmail.com>>:
>>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> About the FreeBSD VM, Holger Freyther worked on it so
>>>>>> he's the best person to answer. I think some people used
>>>>>> it and it was at least partially working.
>>>>> That’s my impression. The VMMaker contains some FreeBSD
>>>>> classes but I have the impression that they are not
>>>>> complete (and probably outdated).
>>>>>
>>>>>>
>>>>>> About your NativeBoost bug on openSolaris, need more
>>>>>> information:
>>>>>>
>>>>>> - Can you confirm that you use an intel processor on your
>>>>>> openSolaris machine ? I assume that yes but I ask because
>>>>>> solaris were typically running on other processors.
>>>>>> NativeBoost, as of today, works only with intel processor.
>>>>>>
>>>>> Yes, my Sun Ultra 24 is an Intel based Workstation (Q9300).
>>>>>
>>>>>> - Do you build the Cog VM or Stack VM ? I mean
>>>>>> PharoVMBuild or PharoSVMBuild ? I think the PharoSVMBuild
>>>>>> does not include NativeBoost by default, that may be your
>>>>>> problem. There's a fix somewhere...
>>>>>>
>>>>> PharoVM from "branch 'master' of
>>>>> https://github.com/pharo-project/pharo-vm" (thus Cog VM).
>>>>>
>>>>>
>>>>> I would like to fold back any changes into the svn master
>>>>> repository for Cog. What are the diffs? (If you have time
>>>>> to send me the diffs that would save me a lot of time).
>>>> I don’t know whether there is much to harvest from what I did.
>>>> As far as I remember most of my work was hacking the generator
>>>> image created by the pharo vm scripts (for my Mac) in order to make
>>>> the resulting C code to compile under openindiana. The basis
>>>> for Solaris was already there (and as far as I can see it is
>>>> also in the Squeak VM sources). I only tweaked some definitions
>>>> and includes.
>>>> I will look at my notes tomorrow and will post if I will find
>>>> something relevant.
>>>>
>>>> I am curios about the future of the PharoVM. The main
>>>> development of the VM seem to happen in the SqueakVM (by you).
>>>> Getting the Spur changes into the PharoVM seem to be a lot of work.
>>>>
>>>>
>>>> Note that this will happen (or is already happening). Esteban is
>>>> working on building the Spur version of Pharo, so he is doing this
>>>> work. But actually it *isn't* that much work. There is basically
>>>> a trio of new memory management files for each platform, e.g.
>>>> platforms/unix/vm/sqUnixSpurMemory.c, and a new source tree for the
>>>> spur vm, spursrc/vm. The system is already set up to build
>>>> multiple VMs (at least the svn tree is).
>>>
>>>
>>> Yes, this is already done. We are building spur VMs and images since
>>> awhile now. You can find all the related jobs here:
>>>
>>> https://ci.inria.fr/pharo/view/4.0-VM-Spur/
>> If I follow this link and what is being used there brings me to the
>> ordinary PharoVm project on github:
>> https://github.com/pharo-project/pharo-vm
>> There are three branches: master, develop and spur64. Which one is
>> being used to build PharoVM-spur32?
>>
>>>
>>> And as Eliot says… is not *much* work… except when it is :)
>>> In fact, we were planning to release Pharo 4 (next week) with a Spur
>>> VM, but we didn’t finish all the small things around. So we will
>>> release next July (or around) a Pharo 4S (S, for Spur) with
>>> “official” spur support. We do not want to stay to much time in
>>> older versions. Also, our development process is different
>> This explanation irritates me: Pharo 4 will be released soon with a
>> Spur VM? And then around summer Pharo 4S? Isn't it a contradiction?
>>
>>> than squeak, AFAIK… we drop backward compatibility in a regular
>>> basis. Which basically means we will move to spur and we will drop
>>> support for older versions.
>> That's OK, but I am still, hmm say confused, because Eliot is
>> changing A LOT (just look at what has been released during the last
>> days), but PharoVM hasn't been
>> changed for some days (I am following the master branch closely). So
>> there is a rapid development in the Cog branch of the SqueakVM. The
>> changes in the PharoVM are much slower (at least as I recognise it).
>
>
> It may seem like I'm changing a lot, but I am /not/ changing the base
> and Spur VMs much. I am only fixing bugs I. spur. That's because I'm
> stabilising the VM for the Squeak 5 release.
>
> The changes are in two areas that are as yet unreleased. One area is
> the JIT for ARM that Tim and I are working on. The other area is
> Sista, the speculative inliner, that Clément and I are working on.
>
Ah, Ok. That's a good explanation, indeed.
Regards
Andreas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/vm-dev/attachments/20150403/0ee350f4/attachment.htm
More information about the Vm-dev
mailing list