Hi guys, 2010/7/16 mattschinkel <[email protected]>: > The other thing to do is to get JALv2 compiler to support arm. If > JALv2 supports arm, will your extension board become obsolete?
Now you mention this (and although you meant atmel), it is good to share my current view on JALv2-C. I've done quite a lot of research on this and although it is probably quite a lot of work, I think it is do-able. However there are some limitations: - variables need to be declared in JAL, so a device file is needed for every target (in contrast with JAT, which can rely on the definitions in the C header). - addressing of JAL is limited to 16 bits and this is probably not easy to change. So probably not easy (if possible) to support 32 bit devices like ARM... Besides this, a specific target chip needs both a JAL device file and stubs to access C library functions. These are closely related and creating and maintaining will require a major effort... Joep. -- You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jallib?hl=en.
