<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Sep 26, 2016 at 8:50 PM, Eliot Miranda <span dir="ltr"><<a href="mailto:eliot.miranda@gmail.com" target="_blank">eliot.miranda@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <br><div dir="ltr">Hi Fabio,<div class="gmail_extra"><br><div class="gmail_quote">On Sun, Sep 25, 2016 at 12:10 PM, Fabio Niephaus <span dir="ltr"><<a href="mailto:lists@fniephaus.com" target="_blank">lists@fniephaus.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">Hi Eliot,<div><br></div><div>I've created a GitHub release for 201608171728 (see [1]) which is</div><div>considered to be stable. Feel free to add a changelog if you have some</div><div>time. You can find all commits after r3732 at [2].</div></div></blockquote><div><br></div><div>Thanks, will do.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div>Is there any particular milestone for the next release?</div></div></blockquote><div><br></div><div>Looking through my emails I see the following for Squeak 6.0:</div><div><br></div><span style="color:rgb(0,0,0);font-size:12.800000190734863px">"For </span><span style="color:rgb(0,0,0);font-size:12.800000190734863px">6.0</span><span style="color:rgb(0,0,0);font-size:12.800000190734863px"> I'm hoping we will do</span><br style="color:rgb(0,0,0);font-size:12.800000190734863px"><br style="color:rgb(0,0,0);font-size:12.800000190734863px"><span style="color:rgb(0,0,0);font-size:12.800000190734863px">- the Sista bytecode set (with backwards compatibility support for the existing set). This gives us 32k literals,</span><br style="color:rgb(0,0,0);font-size:12.800000190734863px"><span style="color:rgb(0,0,0);font-size:12.800000190734863px">- FullBlockClosure, which means I depended method objects for blocks, and hence (slightly) faster block activation</span><br style="color:rgb(0,0,0);font-size:12.800000190734863px"><span style="color:rgb(0,0,0);font-size:12.800000190734863px">- read-only objects and hence read-only literals</span><br style="color:rgb(0,0,0);font-size:12.800000190734863px"><br style="color:rgb(0,0,0);font-size:12.800000190734863px"><div><span style="color:rgb(0,0,0);font-size:12.800000190734863px">These three provide the necessary support for the image-level Scorch adaptive optimiser. This will be demonstrated at ESUG in Prague and productized by next year"</span></div><div><span style="color:rgb(0,0,0);font-size:12.800000190734863px"><br></span></div><div><font color="#000000"><span style="font-size:12.800000190734863px">Clément and I have already put the byte code set and full block support into the latest 32-bit Spur VM source. I should remember to put these into the 64-bit ones too. I think </span></font><span style="color:rgb(0,0,0);font-size:12.800000190734863px">Clément has added read-only-object support to the Pharo VM. The Squeak VM will follow soon.</span></div><div><span style="color:rgb(0,0,0);font-size:12.800000190734863px"><br></span></div><div><span style="color:rgb(0,0,0);font-size:12.800000190734863px">So yes, these </span><font color="#000000"><span style="font-size:12.800000190734863px">three, Sista Bytecode Set as secondary byte code set, FullBlockClosure support and read-only-object support are the major items for the next release.</span></font></div><div><br></div><div> </div></div></div></div></blockquote><div><br></div><div>Hi...</div><div><br></div><div>Some details.</div><div><br></div><div>I have integrated these 3 features, at the exception of the read-only literals, in the Pharo image. I need to check to make sure all the features are enabled in the Pharo VM.</div><div><br></div><div>For read-only objects I have some SUnit tests proving that it works, but it needs further testing. The next step is read-only literals, which leads to the question, will compiled method and compiled block be read-only ? I think they should.</div><div><br></div><div>For FullBlockClosure and the new bytecode set, I have been using them for weeks without any issues. I implemented the FullBlockClosure support in the Opal compiler, one needs to implement something similar in the Squeak Compiler. It may require some change in the debuggerMethodMap. If one is willing to do so, he may want to contact me as there as a couple details that may be useful to be time-efficient.</div><div><br></div><div>These features are important for the Sista architecture. I don't need to load any more dependencies in the Pharo image to have the sista framework running, though the latest SistaVM is broken *again* (Something related to mustBeBoolean, it could be mcpc to bcpc mapping). </div><div><br></div><div>This semester I teach a lot and I write my phd, but I try to make progress on the sista every week. Once all the benchmarks from my suite are running without crashes nor slow-down with the latest Sista VM I will do another call for contributors and make an open beta. This will happen before Christmas. </div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div>Best,<br></div><div>Fabio<br><div><br></div><div>[1] <a href="https://github.com/OpenSmalltalk/opensmalltalk-vm/releases/tag/201608171728" target="_blank">https://github.com/OpenSma<wbr>lltalk/opensmalltalk-vm/releas<wbr>es/tag/201608171728</a></div><div>[2] <a href="https://github.com/OpenSmalltalk/opensmalltalk-vm/compare/r3732...201608171728" target="_blank">https://github.com/OpenSma<wbr>lltalk/opensmalltalk-vm/compar<wbr>e/r3732...201608171728</a></div></div></div></blockquote><div><br></div><div>cheers,</div><div>Eliot</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div><div><span><font color="#888888"><br><div>-- <br></div></font></span><div><div><br><div class="gmail_quote"><div dir="ltr">On Fri, Sep 23, 2016 at 12:16 AM Fabio Niephaus <<a href="mailto:lists@fniephaus.com" target="_blank">lists@fniephaus.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><span style="color:rgb(33,33,33);font-family:'helvetica neue',helvetica,arial,sans-serif;font-size:13px">Hi Eliot,</span><div style="color:rgb(33,33,33);font-family:'helvetica neue',helvetica,arial,sans-serif;font-size:13px">I am currently traveling, but I'm happy to take care of this next week.</div><div style="color:rgb(33,33,33);font-family:'helvetica neue',helvetica,arial,sans-serif;font-size:13px">The procedure is really simple: basically you need to create a Git tag [1] which you can then turn into a GitHub release, or you can just do all of this in one step using GitHub's UI (see [2]).</div><div style="color:rgb(33,33,33);font-family:'helvetica neue',helvetica,arial,sans-serif;font-size:13px"><br></div><div style="color:rgb(33,33,33);font-family:'helvetica neue',helvetica,arial,sans-serif;font-size:13px">Best,</div><div style="color:rgb(33,33,33);font-family:'helvetica neue',helvetica,arial,sans-serif;font-size:13px">Fabio</div><div style="color:rgb(33,33,33);font-family:'helvetica neue',helvetica,arial,sans-serif;font-size:13px"><br></div><div style="color:rgb(33,33,33);font-family:'helvetica neue',helvetica,arial,sans-serif;font-size:13px">[1] <a href="https://git-scm.com/book/en/v2/Git-Basics-Tagging#Creating-Tags" target="_blank">https://git-scm.com/book/e<wbr>n/v2/Git-Basics-Tagging#Creati<wbr>ng-Tags</a></div><div style="color:rgb(33,33,33);font-family:'helvetica neue',helvetica,arial,sans-serif;font-size:13px">[2] <a href="https://help.github.com/articles/creating-releases/" target="_blank">https://help.github.com/ar<wbr>ticles/creating-releases/</a></div><br></div><div dir="ltr"><div class="gmail_quote"><div dir="ltr">On Thu, Sep 22, 2016 at 11:38 PM Eliot Miranda <<a href="mailto:eliot.miranda@gmail.com" target="_blank">eliot.miranda@gmail.com</a>> wrote:<br></div></div></div><div dir="ltr"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div>Hi All, Hi Fabio,</div><div><br></div><div> if one looks at the Releases tab on <a href="https://github.com/OpenSmalltalk/opensmalltalk-vm" target="_blank">https://github.com/OpenSmal<wbr>ltalk/opensmalltalk-vm</a> it says there is only one release, the r3732 release from August when we moved to github. Can we mark the 5.1 release as a second release? How is this done?</div><br><div><div dir="ltr"><div><span style="font-size:small;border-collapse:separate"><div>_,,,^..^,,,_<br></div><div>best, Eliot</div></span></div></div></div>
</div>
</blockquote></div></div></blockquote></div></div></div></div></div></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div><div dir="ltr"><div><span style="font-size:small;border-collapse:separate"><div>_,,,^..^,,,_<br></div><div>best, Eliot</div></span></div></div></div>
</div></div>
<br></blockquote></div><br></div></div>