I think he saying that if is possible to take the assembler code produced by a C compiler for other targets and to put it in JALv2 for good. And then use JALv2 exclusively. If entire Jallib code is translated in assembler for Cortex (e.g.), then that assembler can be stored in JALv2 compiler, so, Kyle don't need to waste time and resources to learn a new assembler for a new target. And you don't need anymore the translator and the C compiler - just once. I understood right Matt?
Vasi(funlw65) On May 21, 11:03 pm, Joep Suijs <[email protected]> wrote: > Hi Matt, > > 2010/5/21 mattschinkel <[email protected]>: > > > One suggestion I had was to take the resulting ASM from Joep's project > > and place it into the JalV2 Compiler. I know nothing about this stuff > > however, but if it is possible it may save you from writing too much > > ASM. > > I'm afraid I don't understand what you suggest. > The translator outputs C that can be fed into a C compiler. If you put > this into the pic18 C-compiler the output will run on an 18F chip, but > the code will be slower and probably larger then the code generated by > the JAL compiler (apart from language conformance and quality). > > 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 > athttp://groups.google.com/group/jallib?hl=en. -- 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.
