Re: [Sdcc-user] Status of PIC16 port

[George M. G. <gga...@co...>]

Eric,

I am using the PIC16 port with 18F252 chips. I use a simple 
multi-tasking that handles the device
initialization and I/O. The only drawback to using SDCC is it does not 
produce reentrant code which
limits me to one "C" task (plan to remove this restriction soon). Code 
optimization is very good.
Data access suffers from PIC limitations, lots of bank selects.

The developers are very responsive to user problem reports.

Given the current state of SDCC I use it for personal projects such as 
robots and home
automation and definitely not use it for industrial or medical products.

George


Eric wrote:

>Hello! I'm starting an embedded project over the next few days that
>needs to be finished by the end of the month, and I'm looking for a
>gpl'd C compiler to use; I'm planning on using either the PIC14 or PIC16
>(all I really care about is ease of in-circuit prorammability at the
>moment, and the PIC18F series looks easy enough, given the proliferation
>of hardware programmer schematics available). 
>
>I can't find, however, a good summary of the PIC14 and PIC16 support by
>SDCC; has anyone actually used these ports for pic development, and
>perhapse could offer some tips on getting started (and what things I
>should watch out for?) 
>
>Thanks!
>		...Eric
>
>
>-------------------------------------------------------
>The SF.Net email is sponsored by: Beat the post-holiday blues
>Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
>It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
>_______________________________________________
>Sdcc-user mailing list
>Sdc...@li...
>https://lists.sourceforge.net/lists/listinfo/sdcc-user
>
>  
>