Understanding .lst file

[pic_girl]

Hi. I am new to using the CCC PCM Compiler. I have been programming Microchip's midrange microcontrollers for the past two years using the RISC assembly language. I have just switched to programming in C using the CCS compiler with MPLAB IDE. Having done the assembly and switching over to C, it has been difficult for me because I am trying to fully understand the .LST file. I would like to know how the compiler pulls together data from the Microcontroller's register file map in their data sheet, to CCS's header file, and finally how it is compiled into assembly .LST file that I see. For example, I have been programming the PIC16F88 and, as a simple example, I want to set RA1 high. In my C code I have:
output_bit(PIN_A1,1);
The datasheet for the Pic16f88 says PortA is in bank 0 at file register 05h.

CCS's 16f88.h header file defines the individual porta pins, with RA1 being:
#define PIN_A1 41

In the .LST file, where I have used the command
output_bit(PIN_A1,1);
it shows :
BSF 05.1

I can see that the datasheet defines PORTA at address 05h and bsf 05.1 would set RA1 high, if I am understanding that correctly. However, how does this correspond to the header file and where could I find more information on mapping the C code, with the .LST file, with the header file, and the datatsheet for the microcontroller? Any help understanding this would be great!

[PCM programmer]

[Ttelmah]

Realistically, you are trying to look beyond anything you should need to know. If you want to access a bit on different register, then just use #bit, or #byte to define it, and access it yourself, without using the standard functions. Touching the processor header file is only necessary if CCS get it wrong, otherwise it is better to leave this alone, and add your own definitions, since changing the file makes the code 'non standard', and effectively uncompilable for other people using the compiler (unless they too have your modifications). The list file is complete in it's own right (turn off the 'nolist' option to give the full printout). The 'output_bit' function (and the output_high, and output_low versions), are just macros designed to _hide_ the real accesses to the port from you. The format for the data, is simply the port address*8, plus the bit address, but they are not warranted to work for any addresses other than those included in the header, so it should never be necessary/sensible to generate these numbers. Remember also, that the output of the functions will change if you have 'standard_io' enabled, instead of 'fast_io', since then the compiler will automatically control the TRIS register as well as the IO register itself.
The actual data determining what features are supported for a processor, are in the file 'devices.dat'. Some can be edited with the device editor. Changing the header file on it's own, will just result in code that is unlikely to work...

Best Wishes