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

RM57L843: Rebuilding rtsv7R4_A_le_v3D16_eabi.lib

Marcio Borges
Expert 1950 points
Part Number: RM57L843

Hello,

We have a safety requirement to do not use source code that cannot be verified/inspected.

The linker includes the libc.a, which is replaced by "rtsv7R4_A_le_v3D16_eabi.lib" and the source code is provided in "ti\ccs1220\ccs\tools\compiler\ti-cgt-arm_20.2.7.LTS\lib\".

I deleted "rtsv7R4_A_le_v3D16_eabi.lib" to force CCS to rebuild it and the new file e different from the previous file (in size and contents). Does it mean the source code provided is not the same as the binary?

Best regards,

Marcio.

  • 0
    TI__Guru**** 249680 points
    Marcio Borges said:
    Does it mean the source code provided is not the same as the binary?

    No.  The object files in the library contain lots of meta-data (debug information, symbol tables, etc.) that is not loaded to the target.  It is typical for this meta-data to contain differences.

    Thanks and regards,

    -George

  • 0 in reply to George Mock
    Expert 1950 points

    Hello. Thank for the response.

    What thing changes the meta-data you mention ? Do you mean timestamps? Do you mean that CCS has switches that modify the rtsv7R4_A_le_v3D16_eabi.lib?

    Does the lib has a safety analysis report?

    Our concerns is to use the lib on a safety critical software.

    We have the source code and we can inspect it (at least the pieces we use, like autoinit). The first step was to rebuild the lib - to ensure we are looking to the correct source code. But we've got a different result. If the result depends on things that we can not control it is not good start.

    Best regards,

  • +1 in reply to Marcio Borges
    TI__Guru**** 249680 points
    Marcio Borges said:
    What thing changes the meta-data you mention ?

    It defies easy description.  These changes occur independent of the build options used.  I presume your method of comparison is a simple diff of the library files.  TI does not document or test for the constraint that the same source code, built the same way, must create an object file that is bit identical to the previous build. 

    Marcio Borges said:
    Does the lib has a safety analysis report?

    No.

    Marcio Borges said:
    The first step was to rebuild the lib - to ensure we are looking to the correct source code.

    The library source code supplied with the compiler is used to build the libraries also supplied with the compiler.

    Thanks and regards,

    -George