[Vm-dev] Integer comparition primitive failures on Cog

Mariano Martinez Peck marianopeck at gmail.com
Mon May 2 16:18:45 UTC 2011


On Mon, May 2, 2011 at 6:11 PM, Eliot Miranda <eliot.miranda at gmail.com>wrote:

>
> No.  Instead certain compact incomes should be mandated.  It is absurd to
> throw away performance and expend effort supporting complexity for
> flexibility that is essentially never used and in maintaining a scheme that
> is only partially effective.
>

+9999

Compact classes didn't change in the last....how many years?
In fact, (and I have already sent an email with this) there are only 15
compact classes. This mean that we can even be using 4 bits instead of 5.


> Eliot (phone)
>
> On May 2, 2011, at 7:20 AM, Igor Stasenko <siguctua at gmail.com> wrote:
>
> >
> > On 2 May 2011 15:46, Igor Stasenko <siguctua at gmail.com> wrote:
> >> Btw,
> >>
> >> i don't like this code:
> >>
> >>        self assertClassOf: floatOrInt
> >>                is: (objectMemory splObj: ClassFloat)
> >>                compactClassIndex: ClassFloatCompactIndex.
> >>
> >
> > btw, Cog is suspectible to have bugs if during run time you will
> > change a class to be no longer compact or
> > (and then installing a different class to be compact on same compact
> > classes array index as before).
> >
> > To avoid that, there should be a primitive which should refresh
> > compact indices for most used classes,
> > to avoid bugs.
> >
> > (The StackInterpreter>>checkAssumedCompactClasses should be run each
> > time when some class become (un)compact).
> >
> > --
> > Best regards,
> > Igor Stasenko AKA sig.
>



-- 
Mariano
http://marianopeck.wordpress.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/vm-dev/attachments/20110502/4e1d3566/attachment.htm


More information about the Vm-dev mailing list