• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 83 subscribers
  • Views 733 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.

Compiler/TMS320F28377D: Warning #99922 when using custom built library

Sheldon He
Expert 8585 points
Part Number: TMS320F28377D


Tool/software: TI C/C++ Compiler

Hi expert,

My cutomer is using F28377D, they built their own library and would like to use them.

When calling function from this library, below error is given. Could you hep us understanding thet?

warning #99922: C:\Users\CHRIST~2.ZHE\AppData\Local\Temp\{7E275D8D-F860-476E-A338-8140264F5023}: Invalid CIE reference 0xff000000 for the FDE at offset 0x00003e19 in the .debug_frame section()

Thanks

Sheldon

  • 0 in reply to Rajaravi Krishna Katta
    TI__Expert 8585 points

    Hi Katta,

    I'd like more details here regarding this issue.

    Their own library is compiled with 18.12.1.LTS and if application is build with 18.1.3.LTS/18.12.1.LTS, no warning will raise. But 16.9.3.LTS will definitely give the warning.

    Some my customer's question:

    1. Is compatibility of compiler the root cause? And this issue start from 16.9.6.LTS.

    2. Should the compiler version used for application be higher than that for library? Or newer than 16.9.6.LTS will be enough?

    3. Which compile did TI usually use for building library?

    4. Do you have any suggestion for compatibility of a common library file?

    Thanks

    Sheldon

  • 0 in reply to Sheldon He
    TI__Guru**** 251180 points

    A key rule to understand is expressed with this pseudo-code ...

    version(linker) >= version(*.obj *.lib)

    That says the version of the linker must be greater than or equal to the version of the tools used to build any object file or library the linker sees.  The reason is that a newer version of the compiler/assembler may put information in the object file (often in the debug information) an older linker does not expect.  

    In your specific case, the version 16.9.3.LTS linker complains when it sees some unexpected debug information in one or more object files built with version 18.12.1.LTS

    The only solution is to use the newer linker.

    Thanks and regards,

    -George