This is what I thought too, John. But can't compilers try different
"placements"? I mean, if one placement doesn't work, move the functions
around and try a different one.

It what you said is true, I guess the solution to it, or the way to avoid
the problem, is to try to make the size of the functions small. Is that
true? I've got to try.

Please correct us, anyone, if we are not heading to the right direction.

Thank you.
Tony

----- Original Message -----
From: "John Walshe" <John.Walshe@INPACTMICRO.COM>
To: <PICLIST@MITVMA.MIT.EDU>
Sent: Wednesday, September 26, 2001 12:54 PM
Subject: Re: [PIC]: Why good code doesn't compile?


> Hi Tony,
>     This is my understanding of it - so anyone please correct me if I'm
> wrong.
>
>     I'm hitting a similar problem at the moment and have tracked it down
to
> the fact that compiler wants to put your code into program space, based on
> the sizes of your code segments. When you deleted those lines in your code
> that section changed size. The compiler then reorganised the way in which
it
> stuffs the code into the chip - based on section sizes and now finds that
> with the new order it can't fit it.
>
> If anyone know how to direct the compiler to change this order please let
us
> know
>
> John
>
> --
> http://www.piclist.com hint: The PICList is archived three different
> ways.  See http://www.piclist.com/#archives for details.
>
>

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.