Counting number of instructions in CCS C

[vsmGuy]

I would like to find out, *without* opening the assembly listing, the number of instructions for a line ( or a number of lines ) in CCS C.

Is this possible ( even in conjuction with tools like MPLAB using the plugin )?

For example,

1. I want to find out how many instructions

Code:

delay_us(200);

generates

2. I want to find out how many instructions

Code:

set_timer1(0);
delay_us(200);

generates

3. Then, I would like to count the number of clock cycles it took to execute each function,  *without* opening the assembly listing

[oldvan]

1.1) 

Code:

       delay_us(200);

Compile.  Note the number of bytes of ROM used.

1.2) 

Code:

//     delay_us(200);

Compile.  Note the number of bytes of ROM used.

1.3) Subtract.


2)  See example given in 1).


3)  ?? Maybe asking a bit much there.

[rajudp]

check the sta file

[TomJackson69]

Hello,

Without read the assembly listing for counting the number of instructions is only guessing. Each programmer write program difference from each other, therefore, one suggestion may not be other want.

For calculate (or guessing) number of instruction during RUN TIME. One could use a TIMER to count the clock cycles for a function being executed and find the number of instructions according to the frequency of the uP running. This way one could get the number of instructions very close to real (error account by some instructions like MOVFF …).

For example:

Define a variable “NUMBER_OF_INSTRUCTION” large enough to hold the counting.

Your function()
{
   Initial TIMER      // to start timer counter
   …
   …         // function body
   …
   Read the timer      // *** make sure the timer don’t roll over *** see note below

Here one could calculate the number of instruction and put it in NUMBER_OF_INSTRUCTION variable. And print out on the LCD or use debug to watch the NUMBER_OF_INSTRUCTION variable.

// remember, this method only gives a proximate number of instruction but one does not have to open the assembly listing to count. If you call another function in your function, the number of instruction still count.
}

One caution should be note: If the function is too long, make sure you know when the TIMER over flow, that way you don’t miss the counter. You could use TIMER INT.

Remember to remove the TESTING instructions from your routine after test.

Tom

[vsmGuy]

I appreciate your post TomJackson69!

In fact, you got the concept bang on - only thing is - in MPLAB you can set up a instruction timer without adding any code to your firmware. I had forgotten how to set it up but found it again on the net.