On Apr 19, 5:34 am, Joep Suijs <[email protected]> wrote: > Hi Vasi, > > 2010/4/19 funlw65 <[email protected]>: > > > A library translation to SDCC must be made by hand (at the lowest > > level possible) and must be very efficient due to poor performance of > > SDCC compiler. > > Due to the limitations of the target devices, not SDCC. I have not > worked with SDCC, but have no reason to suggest it is not a good > compiler.
Indeed the PIC 10/12/16 or any similar CPU are particularly ill- suited to C. The 18F is barely suitable for C. That is why JAL is so good for PIC 10/12/16/18. C design needs efficient indirect addressing, user manipulation of real pointers, single Program/Data space (not Harvard) and stack in RAM. It always amazed me people choosing 8051 + C. Far better a different mpu if you want C or using Assembler. Actually It always amazed me how popular 8051 became ( I debugged an ASM math library on it in 1983 or 1984 for a colleague). If SDCC is for PIC 8 bit core, that's pointless as it can never be as good as JAL. For ARM, MIPS (PIC32 is MIPS) and many AVR the SDCC is pointless as they are well supported by gcc based c and many linux tools which run well on Windows too. I've used http://sourceforge.net/projects/dev-cpp/ on Windows for ARM, as well as gcc on Debian and Barak Linux distros for x86-Geode ARM and MIPS embedded systems. -- 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.
