• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 83 subscribers
  • Views 315 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

TMS320F28062: compiler version

Yale Li 李耀先
Expert 4660 points
Part Number: TMS320F28062


Depending on the version of the compiler, the compiled HEX file and MAP file are different for the same project. How can we ensure that the hex files generated by different versions of the compiler remain unchanged? As follows:

--

Thanks & Regards

Yale

  • +1
    Mastermind 9470 points
    Yale Li 李耀先 said:
    How can we ensure that the hex files generated by different versions of the compiler remain unchanged?

    What you ask is not possible.

    When the compiler changes it is usually because the vendor (TI) has improved its efficiency. I.e. for the same source code, a smaller number of assembly instructions are generated to implement the behaviour described by the source code. Sometimes a corner case bug might be fixed which also changes the assembly code.

    It is up to the end user through Configuration Management to make sure the same compiler is always used and/or to carefully assess a new compiler's changes.

  • +1
    Mastermind 9470 points

    The good news is that you can stop someone from using the wrong compiler with the following code:

    #if __TI_COMPILER_VERSION__ != 22000000
    #error You have the wrong compiler configured!
#endif

  • +1
    TI__Guru**** 251230 points
    Yale Li 李耀先 said:
    How can we ensure that the hex files generated by different versions of the compiler remain unchanged?

    Kier is correct.  This is not possible.  To be honest, I'm surprised the map file matches as much as it does.  Typically, many changes are seen.

    Thanks and regards,

    -George