[xmlvm-users] [xmlvml-users] Re: .class -> CLR pipeline

[John <jo...@tr...>]

Some slight progress - have managed to cobble together a new
ClrOutputProcess so that .net bytecode is being converted again.
Actually managed to get a "hello world" exe out of it, which was nice.

However a slightly more complicated test trips things up, as the
following jvm instructions don't get translated:
jvm:new
jvm:dup
jvm:astore

jvm:new is interesting as it seems that it's just the first of a
handful of instructions responsible for creating a new object. The clr
on the other hand appears to be one big newobj instruction, so I'm not
sure how to write a suitable transform to do that.

I'm also not sure what the clr equivilents of jvm:dup and jvm:astore are.

Also doesn't seem to cope with anything other than a single .class
file as input at the moment. Any hints on how to deal with these
problems appreciated.


On Sat, Oct 10, 2009 at 8:49 PM, John <jo...@tr...> wrote:
> Hello,
>
> I'm interested in using xmlvm so I can develop jvm and .net vm
> versions of the same app with as much shared code as possible. I've
> been trying to get a basic hello-world example working but always get
> the error "Could not create OutputProcess for target 'EXE'."
>
> A bit of poking around in the source seems to suggest that the EXE and
> CLR pipelines have vanished - in particular
> OutputProcessFactory.createOutputProcess doesn't recognise these
> targets any more. Will these be restored any time soon? What's the
> current status of the clr backend?
>
> Assuming this is just a glitch, can anyone tell me how far along the
> clr backend is? Looking through the jvm2clr directory things look a
> little... sparse. I wouldn't mind helping out but right now I wouldn't
> have a clue where to start.
>
> Regards,
>