[Vm-dev] Fwd: [Pharo-dev] Pharo VM Crash
eliot.miranda at gmail.com
Mon Nov 16 22:38:20 UTC 2015
On Mon, Nov 16, 2015 at 2:28 PM, Nicolai Hess <nicolaihess at gmail.com> wrote:
> 2015-11-16 19:31 GMT+01:00 tim Rowledge <tim at rowledge.org>:
>> >>> Tmp>>tmp
>> >>> [ ^ true ]
>> >>> and I try to execute Tmp new tmp. The VM segfaults.
>> Doesn’t appear to be a problem in a Squeak 5.0 image on a cogvm
> yes, this is only a bug in pharo, with pharos opal compiler.
> btw. squeaks compiler (or pharos other compiler) generate more code than is
> needed for this method. The block actually has no effect. The method could
> return self, but instead it creates an unused closure.
> 13 <8F 00 00 01> closureNumCopied: 0 numArgs: 0 bytes 17 to 17
> 17 <79> return: true
> 18 <87> pop
> 19 <78> returnSelf
We know ;-). What happens when you decompile the Opal compiled version and
what happens when you deocmpile the Squeak version? We're going to leave
the aggressive optimisation to the JIT and Sista.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Vm-dev