xmlvm-users

[xmlvm-users] C Backend

[Kevin G. <ke...@co...>]

So, I've been working away on my little games using the Objective-C backend.
I'm quite comfortable fiddling around with it and the objc-comatlib.
However, I'd like to keep up to date, so I'd like to move to the posix
backend. I have a few questions:

- Do I still write against the Objective C compatibility libraries, I can't
find any Java classes in the xml2c compatibility library?
- Will I get a performance increase in moving? I seem to remember you were
going from a stack based to a register based implementation for posix.
- How do I switch over, is it just a matter of changing the target or is the
output completely different?
- Does it still output an xcode project - which I mangle :)
- Are there missing bits from the posix backend that I'll need? (OpenGL,
Sound Calls, Network, Resource access, Input).

Thanks for any input,

Kev

Re: [xmlvm-users] C Backend

[Markus H. <ma...@ti...>]

Hi,

Am 18.05.2011 um 16:22 schrieb Kevin Glass:

> So, I've been working away on my little games using the Objective-C backend. I'm quite comfortable fiddling around with it and the objc-comatlib. However, I'd like to keep up to date, so I'd like to move to the posix backend. I have a few questions:
> 
> - Do I still write against the Objective C compatibility libraries, I can't find any Java classes in the xml2c compatibility library?
Yes you are using the same Java compatibility classes.

> - Will I get a performance increase in moving? I seem to remember you were going from a stack based to a register based implementation for posix.
CanÄt answer that, but you get garbage collection and don't need to release objects yourself anymore.

> - How do I switch over, is it just a matter of changing the target or is the output completely different?
replace the target iphone with target iphonec.

> - Does it still output an xcode project - which I mangle :)
yes.

> - Are there missing bits from the posix backend that I'll need? (OpenGL, Sound Calls, Network, Resource access, Input).
There is probably much missing, but it gets better every day. :)

> 
> Thanks for any input,
> 
> Kev
> ------------------------------------------------------------------------------
> What Every C/C++ and Fortran developer Should Know!
> Read this article and learn how Intel has extended the reach of its 
> next-generation tools to help Windows* and Linux* C/C++ and Fortran 
> developers boost performance applications - including clusters. 
> http://p.sf.net/sfu/intel-dev2devmay_______________________________________________
> xmlvm-users mailing list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlvm-users

Re: [xmlvm-users] C Backend

[Arno P. <ar...@pu...>]

just to add a few things from my side:


On 5/18/11 7:22 AM, Kevin Glass wrote:
> So, I've been working away on my little games using the Objective-C
> backend. I'm quite comfortable fiddling around with it and the
> objc-comatlib. However, I'd like to keep up to date, so I'd like to move
> to the posix backend. I have a few questions:
>
> - Do I still write against the Objective C compatibility libraries, I
> can't find any Java classes in the xml2c compatibility library?

As Markus pointed out, we still use the same Cocoa Java classes in 
xmlvm/src/xmlvm2objc/compat-lib/java. They should (and eventually will) 
be moved to a different directory since their implementation is not 
dependent on the kind of backend.

> - Will I get a performance increase in moving? I seem to remember you
> were going from a stack based to a register based implementation for posix.

In general, I believe so. We do some funky optimizations such as 
selector coloring and vtable reductions.

> - How do I switch over, is it just a matter of changing the target or is
> the output completely different?

For iOS projects: --target=iphonec
For Android projects: --target=iphonecandroid

> - Does it still output an xcode project - which I mangle :)

Yes, same as before.

> - Are there missing bits from the posix backend that I'll need? (OpenGL,
> Sound Calls, Network, Resource access, Input).

There are still quite a few wrapper missing. However, those can usually 
be easily adopted from the Objective-C backend. In other cases, the C 
backend outpasses the Objective-C backend (e.g., full support of the 
standard J2SE API by the C backend)

Arno