• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 52 subscribers
  • Views 311 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Using various version of c6000 in same executable

Thibaud Barel
Prodigy 20 points

Hi all,

A small question: is there any issues that can happen when mixing the compiler versions in one unique executable: library compiled with a specified version of c6000, and included in a "elf" file compiled with another version ?

Any unexpected behavior to fear ? (apart from all the known bugs of each version)

In our case, we are using c6000 v7.4.10 for the core library while the wrapper is using c6000 v7.2.3. Compiler errata analysis are done in appropriate version for each part.

Thanks for your help

  • 0
    TI__Guru**** 232880 points

    Thibaud Barel said:
    we are using c6000 v7.4.10 for the core library while the wrapper is using c6000 v7.2.3

    While I'm not aware of anything specific, you might see problems.  Here is the important rule you are breaking: The version of the linker must be >= the version of the compiler used to build anything the linker sees.  That's because the newer compiler might encode some new detail in an object file that the older linker has never seen.  We never test for this possibility.  We can't.  At the time the older linker is released, this new object file detail does not exist.

    Thanks and regards,

    -George

  • 0 in reply to George Mock
    Prodigy 20 points

    Thank you, this makes sense indeed.