<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">2014-09-07 16:21 GMT+02:00 David T. Lewis <span dir="ltr"><<a href="mailto:lewis@mail.msen.com" target="_blank">lewis@mail.msen.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Fri, Jul 18, 2014 at 04:01:45PM -0300, Casimiro de Almeida Barreto wrote:<br>
><br>
> On 16-07-2014 00:27, David T. Lewis wrote:<br>
> ><br>
> > I tend to switch back and forth between a variety of VMs and images (Spur, Cog,<br>
> > interpreter VM etc). Lately I have been doing my updates from a format 68002<br>
> > 64-bit image. Just curious, is anybody else out there using a 64-bit image on<br>
> > a regular basis and keeping it updated from the trunk development stream?<br>
> ><br>
><br>
> It works but:<br>
><br>
> a) Seems to be slow (although I'm used to the cogvm which is faster than<br>
> SqueakVM)<br>
> b) Somethings just itch my ears like:<br>
> b.1) Compiler recompileAll fails (and shouldn't)<br>
> b.2) Smalltalk condenseChanges that works for 32bit images work, fails<br>
> in 64bit image.<br>
><br>
> b.2 is not that important but b.1 shows that there is code that cannot<br>
> be re-compiled and it's not a good sign.<br>
><br>
> (using trunk updated 64bit image and 4.10.2-2614_64bit SqueakVM)<br>
><br>
<br>
I fixed a small but nasty bug in one of the primitives that appears to have<br>
been the cause of quite a few problems:<br>
<br>
<a href="http://lists.squeakfoundation.org/pipermail/vm-dev/2014-September/016443.html" target="_blank">http://lists.squeakfoundation.org/pipermail/vm-dev/2014-September/016443.html</a><br>
<br>
With freshly compiled VM, Compiler recompileAll and Smalltalk condenseChanges<br>
are working again in a 64-bit image.<br>
<br>
Dave<br>
<br>
<br></blockquote><div><br></div><div>Ah, the beauty of C signed arithmetic model...<br></div><div>We should try to avoid it as frequently as we can. <br></div></div><br></div></div>