<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<div class="moz-cite-prefix">Am 03.04.15 17:04, schrieb Eliot
Miranda:<br>
</div>
<blockquote
cite="mid:5937BF4B-C7C5-408E-8356-BF7DF29A068E@gmail.com"
type="cite">
<pre wrap=""> </pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div>Hi Andreas,</div>
<div><br>
On Apr 3, 2015, at 4:04 AM, Andreas Wacknitz <<a
moz-do-not-send="true" href="mailto:A.Wacknitz@gmx.de">A.Wacknitz@gmx.de</a>>
wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<meta content="text/html; charset=UTF-8"
http-equiv="Content-Type">
<br>
<div class="moz-cite-prefix">Am 03.04.15 11:13, schrieb
Esteban Lorenzano:<br>
</div>
<blockquote
cite="mid:1C1233AA-9813-45E3-83F7-79AA3908A885@gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8">
<br class="">
<div>
<blockquote type="cite" class="">
<div class="">On 02 Apr 2015, at 19:20, Eliot Miranda
<<a moz-do-not-send="true"
href="mailto:eliot.miranda@gmail.com" class="">eliot.miranda@gmail.com</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div dir="ltr" class="">Hi Andreas,
<div class=""><br class="">
</div>
<div class=""> sorry to be late in replying.
This has been a busy month (I moved house).</div>
<div class="gmail_extra"><br class="">
<div class="gmail_quote">On Sat, Mar 14, 2015 at
10:33 AM, Andreas Wacknitz <span dir="ltr"
class=""><<a moz-do-not-send="true"
href="mailto:a.wacknitz@gmx.de"
target="_blank" class="">a.wacknitz@gmx.de</a>></span>
wrote:<br class="">
<blockquote class="gmail_quote" style="margin:0
0 0 .8ex;border-left:1px #ccc
solid;padding-left:1ex"> <br class="">
<div style="word-wrap:break-word" class="">Hi
Eliot,
<div class=""><br class="">
<div class="">
<blockquote type="cite" class="">
<div class="">Am 11.03.2015 um 23:15
schrieb Eliot Miranda <<a
moz-do-not-send="true"
href="mailto:eliot.miranda@gmail.com"
target="_blank" class="">eliot.miranda@gmail.com</a>>:</div>
<br class="">
<div class="">
<div dir="ltr" class="">HI Andreas,
<div class="gmail_extra"><br
class="">
<div class="gmail_quote">On Wed,
Mar 11, 2015 at 9:55 AM,
Andreas Wacknitz <span
dir="ltr" class=""><<a
moz-do-not-send="true"
href="mailto:a.wacknitz@gmx.de"
target="_blank" class="">a.wacknitz@gmx.de</a>></span>
wrote:<br class="">
<blockquote
class="gmail_quote"
style="margin:0 0 0
.8ex;border-left:1px #ccc
solid;padding-left:1ex"> <br
class="">
<div
style="word-wrap:break-word"
class="">Hi Clement,
<div class=""><br class="">
<div class="">
<blockquote
type="cite" class="">
<div class="">Am
11.03.2015 um
09:23 schrieb
Clément Bera <<a
moz-do-not-send="true" href="mailto:bera.clement@gmail.com"
target="_blank"
class="">bera.clement@gmail.com</a>>:</div>
<br class="">
<div class="">
<div dir="ltr"
class="">Hello,
<div class=""><br
class="">
</div>
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.</div>
</div>
</blockquote>
That’s my impression.
The VMMaker contains
some FreeBSD classes
but I have the
impression that they
are not complete (and
probably outdated).</div>
<div class=""><br
class="">
<blockquote
type="cite" class="">
<div class="">
<div dir="ltr"
class="">
<div class=""><br
class="">
</div>
<div class="">About
your
NativeBoost
bug on
openSolaris,
need more
information:</div>
<div class=""><br
class="">
</div>
<div class="">-
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.</div>
<div class=""><br
class="">
</div>
</div>
</div>
</blockquote>
Yes, my Sun Ultra 24
is an Intel based
Workstation (Q9300).</div>
<div class=""><br
class="">
<blockquote
type="cite" class="">
<div class="">
<div dir="ltr"
class="">
<div class="">-
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...</div>
<div class=""><br
class="">
</div>
</div>
</div>
</blockquote>
PharoVM from "branch
'master' of <a
moz-do-not-send="true"
href="https://github.com/pharo-project/pharo-vm" target="_blank"
class="">https://github.com/pharo-project/pharo-vm</a>" (thus
Cog VM).</div>
</div>
</div>
</blockquote>
<div class=""><br class="">
</div>
<div class="">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).</div>
</div>
</div>
</div>
</div>
</blockquote>
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</div>
<div class="">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.</div>
<div class="">I will look at my notes
tomorrow and will post if I will find
something relevant.</div>
<div class=""><br class="">
</div>
<div class="">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.</div>
</div>
</div>
</blockquote>
<div class=""><br class="">
</div>
<div class="">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).</div>
</div>
</div>
</div>
</div>
</blockquote>
<div><br class="">
</div>
<div><br class="">
</div>
<div>Yes, this is already done. We are building spur VMs
and images since awhile now. You can find all the
related jobs here: </div>
<div><br class="">
</div>
<div><a moz-do-not-send="true"
href="https://ci.inria.fr/pharo/view/4.0-VM-Spur/"
class="">https://ci.inria.fr/pharo/view/4.0-VM-Spur/</a></div>
</div>
</blockquote>
If I follow this link and what is being used there brings me
to the ordinary PharoVm project on github:<br>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="https://github.com/pharo-project/pharo-vm">https://github.com/pharo-project/pharo-vm</a><br>
There are three branches: master, develop and spur64. Which
one is being used to build PharoVM-spur32?<br>
<br>
<blockquote
cite="mid:1C1233AA-9813-45E3-83F7-79AA3908A885@gmail.com"
type="cite">
<div>
<div><br class="">
</div>
<div>And as Eliot says… is not *much* work… except when it
is :)</div>
<div>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 </div>
</div>
</blockquote>
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?<br>
<br>
<blockquote
cite="mid:1C1233AA-9813-45E3-83F7-79AA3908A885@gmail.com"
type="cite">
<div>
<div>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. <br>
</div>
</div>
</blockquote>
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<br>
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).<br>
</div>
</blockquote>
<div><br>
</div>
<div><br>
</div>
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.
<div><br>
</div>
<div>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.
<div><br>
</div>
</div>
</blockquote>
Ah, Ok. That's a good explanation, indeed.<br>
<br>
Regards<br>
Andreas<br>
<br>
</body>
</html>