• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 82 subscribers
  • Views 115 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.

TMS320F28384D: The compiler CQKIT coverage test

Luke Chen
Expert 5090 points
Part Number: TMS320F28384D

Tool/software:

Hi champs,

My customer has below questions about compiler CQKIT coverage test,

  1. Is the purpose of coverage test to check whether the user code contains the compiler bug?
  2. Should customer run user code then collect line and branch coverage information?
  3. Do we support code coverage tool and how to use this tool?

Please advise, thanks for your help.

Regards,

Luke

  • +1
    TI__Guru**** 244030 points

    I suspect the customer misunderstands the nature of the coverage check in the CQKIT.  This coverage check is not about how much of the customer source code has undergone testing.  It is about how much of the source code used to implement the compiler, assembler, linker etc. has undergone testing.  For the rest of this post, I'll use the term "compiler" to refer to all the tools delivered with the compiler, including the assembler, linker, etc.

    Before any release, the compiler is thoroughly and extensively tested.  Nonetheless, it is possible that, in the process of compiling customer source code, parts of the compiler which escaped testing get exercised.  The coverage check in the CQKIT is about discovering whether this occurred.  The customer source code is compiled with special binaries that are instrumented to record what parts of the compiler source code are exercised.  These records are compared against what parts of the compiler are exercised during release testing.  If any gaps are discovered, they are addressed.

    Thanks and regards,

    -George