[Vm-dev] VM Maker: VMMaker.oscog-dtl.3123.mcz

Eliot Miranda eliot.miranda at gmail.com
Thu Apr 7 11:22:51 UTC 2022


Hi Marcel,


> On Apr 7, 2022, at 4:17 AM, Marcel Taeumel <marcel.taeumel at hpi.de> wrote:
> 
> 
> Hi Dave, hi Eliot, hi all --
> 
> I think we can still merge this into the next VM release.
> 
> For Squeak 6.0, I only then have to figure out how to produce that new (base) image for the bundles. :-) Probably something in the area of SystemTracer... or I just hack the image header directly? xD

I don’t think you need to anything to the image.  This is a vm property, ie does the vm support multiple bytecode sets or not?  One should be able to run an image that uses only one bytecode set on a vm that supports two.

> 
> Best,
> Marcel
>> Am 03.01.2022 04:32:31 schrieb David T. Lewis <lewis at mail.msen.com>:
>> 
>> 
>> Hi Eliot,
>> 
>> On Sun, Jan 02, 2022 at 01:17:02PM -0800, Eliot Miranda wrote:
>> > 
>> > On Sat, Jan 1, 2022 at 1:07 PM David T. Lewis wrote:
>> > >
>> > > I put VMMaker.oscog-dtl.3124 in the VMM inbox, which includes your
>> > > recommendations along with a few unit tests to cover the format number
>> > > handling.
>> > >
>> > 
>> > Cool. The definition and initialization of the new
>> > StackInterpreter multipleBytecodeSetsActive inst var is missing. I'm
>> > assuming it is an inst var. How should it be initialized? From
>> > MULTIPLEBYTECODESETS or left false by default?
>> > 
>> 
>> multipleBytecodeSetsActive (an inst var in InterpreterPrimitives) is
>> initialized in StackInterpreter>>imageFormatVersionFromSnapshot:
>> while reading the image file header. Otherwise it is only updated by
>> primitiveMultipleBytecodeSetsActive.
>> 
>> The inst var might also need to be initialized to MULTIPLEBYTECODESETS in
>> simulation (I did not do that). In the three new tests in FormatNumberTests,
>> I called #imageFormatVersionFromSnapshot: to set up the test data.
>> 
>> The primitiveMultipleBytecodeSetsActive inst var tells us what the
>> image claims to be requiring, as opposed to MULTIPLEBYTECODESETS
>> which is what the VM is actually capable of supporting. It is used
>> only for reading and writing the image format number and has no other
>> effect on the VM itself.
>> 
>> Dave
>> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/vm-dev/attachments/20220407/48b480c6/attachment.html>


More information about the Vm-dev mailing list