Maybe the problem is in the image, the interpreter VM or the
TwosComplement package, we don't know.  Since it does not appear
likely anyone will be able to investigate it soon, and the nature of
both releases is about all-new VM(s) anyway, we probably should not
hold up the release over this.

In fact, I could make another RC without the recompileAll.  Is it
really necessary?  I don't know any better about its purpose than why
it would be a problem.  I guess anyone could do it on their own if
they wanted..


On Tue, Jul 7, 2015 at 1:31 PM, David T. Lewis <lewis at mail.msen.com> wrote:
> I am away and cannot follow up on this for a while.
>
> My guess would be that there is something wrong in the compiler, and that
> it needs to be fixed (but I cannot check now to find out). I don't know if
> this affects SqueakJS or other VMs.
>
> Dave
>
>> On Tue, Jul 7, 2015 at 7:33 AM, David T. Lewis <lewis at mail.msen.com>
>> wrote:
>>> On Mon, Jul 06, 2015 at 09:46:09PM -0500, Chris Muller wrote:
>>>> Probably the Compiler recompileAll..?
>>>
>>> Confirmed.
>>>
>>> Compiler recompileAll results in an image that crashes the interpreter
>>> VM.
>>> A fully updated trunk image works fine, but recompiling it breaks the
>>> image.
>>
>> Interpreter VM will not be able to run Spur images going forward.  So
>> this is the last possible release to support the Interpreter VM anyway
>> is that right?
>>
>> Maybe it is time to abandon Interpreter VMj?  Or release 4.6 without
>> the recompileAll and release 5.0 with it?
>>
>> Please let me know how you would like to proceed.
>>
>
>