Sorry, Scott:

I did not catch that.  I saw your site some time ago and have been
(Impatiently) waiting for the PIC implementation.  I looked at the
implementation and I liked what I saw for the other controllers.  I was
(actually thinking about starting a GCC for the PIC but then saw your site)
I  have used GCC for the 68HC11&12 and the M68K Coldfire.

Thanks for the update.  If you need help with beta testing or if I can be of
any assistance please feel free to contact me.  On sourcefroge I am
dbergerson@users.sourceforge.net.

Have a wonderful new year.



In theory there is no difference between theory and practice.  In practice
there is a whole bunch of difference.  I pick practice.

Bad things like software bugs do not come one at a time but in bunches and
groups.  My apologies to Mr Shakespeare.

Steve B


-----Original Message-----
From: pic microcontroller discussion list
[mailto:PICLIST@MITVMA.MIT.EDU]On Behalf Of Scott Dattalo
Sent: Monday, December 31, 2001 8:19 PM
To: PICLIST@MITVMA.MIT.EDU
Subject: Re: Porting from one C compiler to another.[PIC]


On Mon, 31 Dec 2001, steve b wrote:

> Is the PIC port of the SDCC completed yet?

No, As I said two posts ago :). Beta ~ March 2002.

If you're anxious to see what's supported, then check out:

http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/sdcc/sdcc/src/regression/

The pic port of SDCC properly compiles every C file on this web page.

The major thing I'll be attacking next is banked RAM. But before this is
solved, I need to write some more infrastructure code to assist in flow
analysis.


Scott

--
http://www.piclist.com#nomail Going offline? Don't AutoReply us!
email listserv@mitvma.mit.edu with SET PICList DIGEST in the body

--
http://www.piclist.com#nomail Going offline? Don't AutoReply us!
email listserv@mitvma.mit.edu with SET PICList DIGEST in the body