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/TMS320F28377S: Defect Tracking for C2000 Compiler v6.2.7

Part Number: TMS320F28377S


Tool/software: TI C/C++ Compiler

Hi,

We are currently using compiler version 6.2.7 in our product and I am trying to understand all the major defects with this version and performing a risk assessment for our product. We went through the online documentation and tried to list all the new features/defects between v6.2.7 and the latest compiler version. But what we cannot clearly identify is all the defect in 6.2.7. For instance if a new defect was entered in version 6.4.0, how do we know if v6.2.7 has the same exposure?  Please see attached for our analysis so far. Is there way to get all the defects in v6.2.7 and the related documentation (classified as major, minor or open etc..)

ThanksCompiler Defect Tracking.xlsx

  • Please read the article Compiler Version Numbers and What They Mean, with a focus on understanding the concept of a related stream of compiler releases, such as the 6.2.x releases.

    Now, add another concept: active streams and inactive streams.  An active stream is a series of compiler releases that is actively maintained, because future releases are planned.  When a bug is reported, the related investigation includes determining whether any active stream has the bug.  The opposite is true of the inactive streams.  Once a stream is declared inactive, no further investigations occur.  For example, the current active streams for the C28x compiler are 18.1.x.LTS, 18.12.x.LTS, and 20.2.x.LTS.  You can see this on the general C2000 compiler releases page

    The last version 6.2.x release is version 6.2.11, which occurred in February 2015.  At that point, this release stream went inactive.  With regard to bugs reported after that time, no investigation occurred about whether it is present in 6.2.x releases.

    So the best record of bugs fixed or known about 6.2.x releases is in the defect history for the last release on the stream, version 6.2.11.

    Thanks and regards,

    -George