On 6/30/06, Richard Latter <[EMAIL PROTECTED]> wrote:
> Hello All,
>
> I have an application which I am writiing for the
> PIC14 range of processors. I have written the
> application in SDCC C. I use the following line:
>
> sdcc -mpic14 -p16f628.c myproc.c
>
> The compiled .asm output seems to be q
Hi Richard,
> I have an application which I am writiing for the
> PIC14 range of processors. I have written the
> application in SDCC C. I use the following line:
>
> sdcc -mpic14 -p16f628.c myproc.c
>
> The compiled .asm output seems to be quite bloated and
> the .hex file is about 1200 bytes i
For a 175 byte program, have the CCS generate assembler and use that as
you base.
George
On Fri, 2006-06-30 at 12:36 +, Richard Latter wrote:
Hello All,
I have an application which I am writiing for the
PIC14 range of processors. I have written the
application in SDCC C. I use the foll
Hi Richard,
I agree very much with your findings. You may also try CC5X and get even
more compact code. However to be fair it has to be mentioned that CCS
and CC5X do not have the ambition of SDCC regarding a more sophisticated
grammar allowing more powerful structures etc. I think that everyt
On 6/30/06, Richard Latter <[EMAIL PROTECTED]> wrote:
> Hello All,
>
> I have an application which I am writiing for the
> PIC14 range of processors. I have written the
> application in SDCC C. I use the following line:
>
> sdcc -mpic14 -p16f628.c myproc.c
>
> The compiled .asm output seems to be q
Hello All,
I have an application which I am writiing for the
PIC14 range of processors. I have written the
application in SDCC C. I use the following line:
sdcc -mpic14 -p16f628.c myproc.c
The compiled .asm output seems to be quite bloated and
the .hex file is about 1200 bytes in length.
I hav
