This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Issue with file specific options and 3.3 project import into 5.4

I found that I am having difficulty producing an "equivalent" build when importing my 3.3 project into 5.4. For files that do not have "file specific options" (use of global compiler settings), the resulting .obj is equivalent via objdiff. However for a file with file specific options, I get differences in the .obj.

In this case, the one file has -02 optimization turned off (NONE), whereas at the project level it has -02 defined, per the Basic Compiler Options dialog box:

"Generate Debug Info: Full Symbolic Debug -g"

Opt Speed vs. Size: "Speed Most Critial (no -ms)"

Opt Level: "NONE" file specific, "-02" (global),

I think this is the first time we have had file specific options when trying to import a 3.3 project. 

We are using C55X and 4.3.1 CGT.

Thanks.

  • To get identical object code, many things must match exactly.  The source code (including all the header files), the compiler version, the compiler options, etc.  In this particular case, I suspect the compiler options are not matching.  Carefully compare the build options the compiler sees in both cases.  Make sure they match exactly.  

    Thanks and regards,

    -George

  • Understood.

    It looks like when the project is imported, the file specific options drops the -g option which is causing the differences in the object file. Normally just the -02 is omitted but the -g remains. The only difference in the file specific options in the 3.3 project is changing optimization level from -O2 to NONE.

    I believe this to be a bug.

    Regards, 

  • Since this problem seems to be in CCS, and not in the compiler, I'll move this thread to the CCS forum.

    Thanks and regards,

    -George

  • Hi,

    Thanks for reporting this. I could reproduce this behavior and filed the bug number SDSCM00047535 (check its status in the link SDOWP in my signature below).

    Sorry for the inconvenience,

    Rafael

  • Also a note that in my CCS 3.3 project, I have a DEBUG and a RELEASE target both with the same file with optimization turned off. However when I set the active configuration to RELEASE in 5.4, the file specific options has optimization enabled in addition to the symbolic debug field being blank. So there seems to be some difference there between the import between the two target configurations...

    Another note, your SDOWP link does not quite work, it cannot look up the database. I had to find a link to it from another post.

    Thanks.