[Vm-dev] Why does CompiledMethod>>#objectAt:put: work no longer
on spur?
Tobias Pape
Das.Linux at gmx.de
Wed Jul 8 13:30:24 UTC 2015
Ok, now I see how this was actually API misuse.
I'll rephrase that.
Best regards
-Tobias
On 25.06.2015, at 14:27, Jakob Reschke <jakob.reschke at student.hpi.de> wrote:
>
> Note that the CompiledMethod header format has changed. That code now
> erases part of the literal counter in the header, if I am not
> mistaken. The primitive implementation prevents modification of the
> literal count explicitly.
>
> Best regards
> Jakob
>
> 2015-06-25 11:59 GMT+02:00 Tobias Pape <Das.Linux at gmx.de>:
>>
>>
>> In V3, this works:
>> | cm |
>> cm := (CompiledMethod newFrom: (ByteString >> #findSubstring:in:startingAt:matchTable:)).
>> cm objectAt: 1 put: (cm header bitAnd: 16r1FF bitInvert).
>>
>> In SPUR, objectAt:put: raises a primitive Failed.
>>
>> Best regards
>> -Tobias
More information about the Vm-dev
mailing list