[squeak-dev] trunk and new vm etiquette

Eliot Miranda eliot.miranda at gmail.com
Tue Jul 21 00:55:07 UTC 2020

Hi All,
    I've just found and fixed a VM bug in an as-yet-unpublished pair of
primitives that replace FloatArrayPlugin>>primitiveAt[Put] and
Float64ArrayPlugin>>primitiveAt[Put].  The new replacement, which allows
two methods (at:[put:]) in FloatArray to relace four methods
(Float32Array>>at:[put:] & Float64Array>>at:[put:]) are some 5 to 10 times
faster than the plugin methods.  The issue is when to publish the
corrections to trunk.

Since the existing VM is broken I don't want to simply push to trunk and
have people inconvenienced by a sudden emergence of failures in the
FoatArrayTests.  However, I do want to push the corrections soon, because
they're a substantial improvement.  So the question is how long should I

Is it OK if I push the fixes to FloatArray and subclasses in a week?  Do
people using trunk keep an eye on the CI builds and upgrade, or would they
appreciate a heads up?  If so, as soon as the AppVeyor builds succeed
for CogVM source as per VMMaker.oscog-eem.2778, I'll let you know and ask
that you upgrade your VM.
best, Eliot
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20200720/16491cd5/attachment.html>

More information about the Squeak-dev mailing list