tms470_4.9.5 compiler giving errant 188-D and 225-D line numbers in CCS 5.2

I cannot reproduce this with a small test case.

How do you determine the actual line number of the warning? 

Do you have any line continuation characters in MiWi.c?

It took me an hour and a half to hack down 5400lines to just these:

long x;
long y;

void PrintChar(unsigned char ch) { }

void Tasks(void)
{
    #if defined(ENABLE_SLEEP)
// The content in this #if clause is the issue, can be commented out or not
//        if( y == 0 )
//        {
//            x = 0;
//        }
    #endif
}

void DumpConnection(unsigned char index)
{
    unsigned char i = 0;
    int j;  // needs to be signed to avoid TS470 warning below

    if( index == 0xFF )
    {
        PrintChar(i);
        ConsolePut(' ');
    }
}

Giving these warnings:

"../188D.c", line 24: warning #225-D: function declared implicitly
          ConsolePut(' ');
          ^

"../188D.c", line 19: warning #179-D: variable "j" was declared but never
          referenced
      int j;  // needs to be signed to avoid TS470 warning below

Thank you for providing a test case, but unfortunately I still can't reproduce the problem.

From inspection of your post, the line numbers reported definitely should be 25 and 20, but that's exactly what I get when I run the TMS470 compiler version 4.9.5 on this test case.

There could conceivably be a bug involving whitespace (I doubt it).  Could you zip this test case and attach that, so that I know I'm working with your exact test case?

What command-line options are you using?

Please find the file attached.

From Properties window, my summary of flags is:

-mv7M4
--code_state=16
--float_support=FPv4SPD16
--abi=eabi
-me
-g
--include_path="C:/ti/ccsv5/tools/compiler/tms470_4.9.5/include"
--include_path="C:/Data/Code/LM4FCommon/CommonLib/trunk"
--include_path="C:/StellarisWare"
--define=css --define=__TMS470__
--define=__LM4F__
--define=TARGET_IS_BLIZZARD_RA1
--define=PART_LM4F232H5QD
--verbose_diagnostics
--diag_warning=225
--display_error_number

When I compile your downloaded 188D.c using v4.9.5 with the options you provide, I get this:

"188D.c", line 24: warning #225-D: function declared implicitly
          ConsolePut(' ');
          ^

"188D.c", line 19: warning #179-D: variable "j" was declared but never
          referenced
      int j;  // needs to be signed to avoid TS470 warning below
          ^

The line numbers match what I see in the file:

pf, I think you're correct, and it is a CTRL-M carriage return (0x0D) without a line feed and not the two characters ^ and M, which is very unusual for Windows.  Using a binary editor on the provided file, it is the only location that has 0x0D without the 0x0A expected on Windows.

I can say you solved this problem of errant line numbers.  I cannot guess how this happend, though the original code came from a third party.  I am pretty sure I did not touch this line - though I touched many others.  I am not sure how to even enter just a line feed.

I search the third party code base I am porting, and this line alone has the missing line feed.  I have deleted the lone \r and just hit return.  The line numbers for errors in the original code now accurate.

I will mark this solved.