<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Hi <br class=""><blockquote type="cite" class="">On 12.04.2018, at 16:05, Eliot Miranda <<a href="mailto:eliot.miranda@gmail.com" class="">eliot.miranda@gmail.com</a>> wrote:<br class=""><br class="">Hi Bert,<br class=""><br class=""><br class="">On Apr 12, 2018, at 6:03 AM, Bert Freudenberg <<a href="mailto:bert@freudenbergs.de" class="">bert@freudenbergs.de</a>> wrote:<br class=""><br class=""><blockquote type="cite" class="">If that's indeed the case we need to make a 64 bit VM for 32 bit images. I think this should be just a matter of picking the right compiler options.<br class=""></blockquote><br class="">How so? AFAIA it is not. It means, for example, changing every memory access for an instance variable from 64 to 32 bits. It is non-trivial.<br class=""></blockquote><div class=""><br class=""></div><div class="">But wasn't that done once already?</div><div class=""><br class=""></div><div class="">I see Squeak 5.7.4.1 (John Macintosh did it I think).</div><div class="">Wich advertises itself as</div><div class=""><img apple-inline="yes" id="18D10F12-7B77-4D3A-8308-572652F01A86" height="21" width="176" apple-width="yes" apple-height="yes" src="cid:891DE8B9-5BF4-43C0-AE3C-4FE4DB2755A0@l.certwifi.com" class=""></div><div class=""><br class=""></div><div class="">and worked very well. Not saying every bits are there for the present (spur etc)</div><div class="">but at least, we have been there already at least once…</div><br class=""><blockquote type="cite" class=""><br class="">What /is/ trivial is detecting that an image's word size is unsupported on a platform and offering to convert it, a process that takes less than a minute for typical images.<br class=""><br class="">If we go this route we would include a headless 64-bit image that converts 32-bit images to 64-bits on 64-bit only systems, and a headless 32-bit image that converts 64-bit images to 32-bits on 32-bit only systems.<br class=""><br class="">IIRC 64 to 32 bit conversion needs to be written, but I think it is trivial compared to building a 64-bit vm for 32-bit images.<br class=""><br class="">Of course this applies only to Spur images. We don't have a way of automatically converting V3 images to Spur. Yo do that going forward we may have to depend on OS virtual machines, but somehow I can't see an ARMv8 Mac supporting x86 VMs like Parallels. This could be the end of an interoperability era.<br class=""><br class=""><blockquote type="cite" class=""><br class="">Otherwise we won't have any way of opening regular 32 bit images on Macs.<br class=""><br class="">- Bert -<br class=""><br class="">On 12 April 2018 at 14:47, Fabio Niephaus <<a href="mailto:lists@fniephaus.com" class="">lists@fniephaus.com</a>> wrote:<br class="">Hi all,<br class=""><br class="">According to [1], Apple has started to alert users when they open a 32-bit app on the Mac and I've seen such a dialog today myself when opening a 32-bit Squeak image.<br class=""><br class="">It looks like it is time to make 64-bit the default, maybe with the next release? The Pharo community is already doing that for quite some time, so I'm wondering if there is any reason not to do the same?<br class=""><br class="">Best,<br class="">Fabio<br class=""><br class="">[1] https://techcrunch.com/2018/04/11/apple-starting-to-alert-users-that-it-will-end-32-bit-app-support/<br class=""><br class=""><br class=""><br class=""><br class=""></blockquote><blockquote type="cite" class=""><br class=""></blockquote><br class=""></blockquote><br class=""></body></html>