[Vm-dev] [Squeak 0007821]: Make generated interpreter code
compatible with Plan9's POSIX C compiler
alex.franchuk at gmail.com
Thu Oct 2 02:23:05 UTC 2014
The version of VMMaker I'm using is VMMaker-dtl.350.
I believe that issue is due to an error on my part. I neglected to test
on plugins, just on the interpreter code (because for now I'm only
porting the barebones interpreter to Plan9). That plugin seems to have
exposed the error. I've posted a fixed change set to the Mantis submission.
On 10/01/2014 09:28 PM, David T. Lewis wrote:
> On Wed, Oct 01, 2014 at 07:24:52PM -0400, David T. Lewis wrote:
>> On Wed, Oct 01, 2014 at 07:36:12AM -0400, David T. Lewis wrote:
>>> This is a new Mantis submission with a change set to address Posix
>>> compliance for generated code.
>>> I expect that the changes would be applicable to both oscog and trunk VMM,
>>> although so far I have only taken a quick look at it in VMM trunk.
>> I am posting this to vm-dev just for the record:
>> Alex Franchuk (alex.franchuk at gmail dot com), the author of the changes
>> submitted in Mantis 7821, has confirmed that his updates are licensed MIT.
>> Alex has also joined the vm-dev list so questions and discussion can take
>> place here.
>> Alex, can you tell me the exact version of VMMaker (the VMMaker.xxxxx.mcz
>> from the repository) that you are using? I ran into a problem when I tried
>> generating the VM sources with your change set applied, but I have also been
>> trying to gradually update the VMMaker package with Eliot Miranda's changes
>> that he is making it the oscog branch, so it is likely that our versions
>> are not in sync. Thanks!
> Attached is the debugger window at the point of failure when generating
> BitBltPlugin from an image with VMMaker-bf.351 loaded, and Plan9-Compat.1.cs
> change set added.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Vm-dev