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/TMS570LS1227: Accurate list of compiler issues

Part Number: TMS570LS1227

Tool/software: TI C/C++ Compiler

We are currently using the 5.2.9 compiler and are trying to evaluate the list of known compiler issues for a safety critical project. There seem to be two sources and little overlap between them.

The first is from the compiler open defects list at http://software-dl.ti.com/codegen/esd/cgt_registered_sw/TMS470/5.2.9/Open_defects.html

The second is from the SDOWP system at https://cqweb.ext.ti.com/cqweb/#/SDO-Web/SDOWP&format=HTML&version=cqwj

In the latter there are reports under "Defects by Target - Open and Fixed" for 5.2.x Compiler.

Where can I find a definitive list of compiler issues that are still open on the 5.2.9 compiler?

Thanks,

Richard

  • It's also worth mentioning that the SDOWP report is very confusing because it only shows the first line of the affected compilers. Take SDSCM00040934 for example. If the incident report is opened, the full list of affected versions is PRU_2.2.0, C6000_8.2.0, ARM_15.12.0.LTS, ARM_5.2.0B1, ARP32_1.0.0B1, C2000_15.12.0.LTS, C2000_6.4.0B1, C6000_7.4.0B1, C6000_8.1.0B1, MSP430_15.12.0.LTS, MSP430_4.4.0B1, PRU_2.1.0, C2000_16.9.0.LTS, ARM_16.9.0.LTS, MSP430_16.9.0.LTS, ARM_18.1.0.LTS, C2000_18.1.0.LTS, MSP430_18.1.0.LTS, C6000_8.3.0, ARM_18.9.0.STS, C2000_18.9.0.STS, MSP430_18.9.0.STS, PRU_2.3.0.

    However, the ARM Compiler know issues report only shows PRU_2.2.0, C6000_8.2.0, ARM_15.12.0.LTS.
  • This deficiency also applies to the two export function (to text, to Excel).
  • TI compiler releases are organized into release streams.  When the first two numbers of the release are the same, they are from the same stream.  For example versions 16.9.9.LTS and 16.9.5.LTS are from the same stream.  Versions 16.9.9.LTS and 18.1.4.LTS are from different streams.  Streams are categorized as active, reactive, and inactive.  Bugs are only fixed on active release streams.  Right now, the TI ARM compiler has 3 active streams: 18.9.x.STS, 18.1.x.LTS, and 16.9.x.LTS.

    When a bug is reported, we check for it only on active streams.  The other release streams are not checked.  It is impractical to do otherwise.  After all, no further releases are planned on the reactive or inactive release streams.

    The Open Defects document, for any given release, is a list of the bugs known as of when the release occurs.  Bugs reported after that point are not added to the document.

    So, for active releases, for the most recent list of bugs known, check the Open Defects for the last release on the stream.  For reactive or inactive releases, the best you can do is check the last release on that stream.

    The best place to check for the latest compiler releases is this page.  

    Richard Burke said:
    In the latter there are reports under "Defects by Target - Open and Fixed" for 5.2.x Compiler.

    I don't see that query.  Of the queries I do see, the information is out-of-date.  I will see about getting these queries removed.

    Thanks and regards,

    -George

  • Thanks for the information, George. We were using the 16.9.x stream but came across a major issue so reverted to the 5.2.x (which I thought was supposed to be LTS).

    From what you have said, the best source seems to be the list of defects provided with the compiler release.