Hi Matt, Vasi, 2010/5/21 funlw65 <[email protected]>: > If entire Jallib code is > translated in assembler for Cortex (e.g.), then that assembler can be > stored in JALv2 compiler Interesting thought...
The converting & store part is easy. An issue however is that the assembler code generated is quite specific: code is generated depending on constants, some code will be left out and it uses fixed memory locations (the compiler starts using memory from the bottom). An other isssue is using the code: how does the compiler know what code part is required and how to call it? And also, the compiler needs to translate the user program into the target assembly, which requires target assembler knowledge. And to look a bit more into this: the compiler translates in two passes: the first one translates JAL into pcode which is target independent. The next step is to translate pcode to target code. So using the pcode for a new target would be ideal for compatibility. Kyle and I will investigate if the current pcode is suitable for c-code generation and - if not - if it can be made suitable. 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.
