Interpretation of the .lst file

[Paul]

Hi,

Sometimes I look at the .lst file to see what the compiler makes of my c. Usually it is easy to see what statements generate what code. I recently had a question about a #USE rs232 that I needed to see the compiled code for. It took me a lot of time to realise that the code for this statement is in the beginning of the main() function and nowhere near the actual #USE rs232 statement in the list file.

My question: could I have known that? Is there a way to 'know' where code is placed?

Thanks,

Paul Holthuizen
PCWH 3.248

[PCM programmer]

See this FAQ article:
http://www.ccsinfo.com/faq.php?page=lst_out_of_order

Some of the initialization code for the #use libraries is put at
the start of main(). For example, that's where the compiler
puts the setup code for the UART if you specify #use rs232().

The code that performs the UART functions is usually placed
inline if it's short, such as the putc() code for a hardware UART.
It's placed under the #use rs232() statement if it's longer code,
such as for a 'soft' UART, or if parity calculations are required, etc.,
because the compiler typically will 'call' that code instead of placing
it inline.