From: Bert D. <dri...@pl...> - 2004-06-01 13:56:16
|
On Tue, 1 Jun 2004, Leonard Garvey wrote: > I'm doing a kind of testing for a 16f877 (and without trying to open > the debate about if a c compiler for a PIC is worthwhile).. > > I still need to fully confirm for myself that alot of the basics are > available (the PIC is pretty basic so most of it can be used with just > the basics of C too).. > > If there are any aspects that I should pay particular attention to, or > anything which might prove helpful (or otherwise) would be greatly > appreciated. > > Its a bit difficult to assess the status of the PIC14 port.. (other > than its not complete). Issues I know about... Sorry, I've not come around to creating test sets yet: - const array references leak two bytes of RAM per array - the compiler is too aggressive eliminating bcf status,5; for example, referring to a TRIS register in a subroutine may leave status<5> set - The "%" operator is not implemented - Passing a const char pointer doesn't generate working code The bcf status,5 issue is the only one that is not obvious from reading the generated assembly. Cheers, -- Bert -- Bert Driehuis -- dri...@pl... -- +31-20-3116119 If the only tool you've got is an axe, every problem looks like fun! |