[Vm-dev] Identity hash for immediate objects in Spur

Nicolas Cellier nicolas.cellier.aka.nice at gmail.com
Wed Nov 26 23:10:03 UTC 2014

Ah, a subject for Andres Valloud certainly...

2014-11-21 16:25 GMT+01:00 Bert Freudenberg <bert at freudenbergs.de>:

> Currently, the identityHash of a SmallInteger is that value itself. The
> hash primitive (75) fails for SmallIntegers.
> For new immediate objects I think the VM needs to answer a hash, because
> it would be inconvenient/expensive to do on the image side.
> The VM could simply re-interpret the bits of the oops as if it was a
> SmallInteger. But it could also pick 22 bits (as for non-immediate objects)
> depending on the immediate class that are likely to make a good hash (*).
> If we do the latter, would it be possible to make the identityHash of
> boxed floats be the same?
> The advantage of this would be that the VM could freely demote a boxed
> float into an immediate one at any time, even if it was held in an identity
> dictionary. That way the image might not have to worry as much about
> normalizing floats (as it has to do now with large integers).
> - Bert -
> (*) For an immediate double, picking the lower 22 bits of the upper 32 bit
> word seems reasonable, taking the 2 least significant bits of exponent and
> 20 most significant bits of the mantissa.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/vm-dev/attachments/20141127/f3d25120/attachment.htm

More information about the Vm-dev mailing list