• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 53 subscribers
  • Views 1060 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.

Accessing the Compiler Defects List

Giles Robnson
Expert 1495 points

Hello

I am trying to access / generate an up-to-date list of the known defects for the C2000 compiler, release 6.1.0.  I have not been able to do this.  So far I have tried:

Starting from page http://processors.wiki.ti.com/index.php/Compiler_Defects_Database I have:

1. Accessed the ClearQuest database using the “readonly” username, but “Public Queries” only goes up to release 6.0.x.

2. Tried to log in to the database using my TI login, which does not work.  Perhaps it is another login, but when I go to https://cqweb.ext.ti.com/pages/SDO-Web.html to create a new account, the link New Account Request takes me to a “Not Found”.

Also:

3. On page http://software-dl.ti.com/codegen/non-esd/downloads/download.htm there is a Defect History document given for release 6.1.0, but this is date April 2012 & so very old.  I know a defect was added to the database recently for a bug we found.

How do I get a current list, and how do I login to the database?

Regards.

  • 0
    TI__Guru**** 249900 points

    The information you want is in a file named DefectHistory.txt.  It comes with every compiler release.  It can be found in the root directory of the compiler installation.  It is also a link available on the C2000 compiler download page.

    Thanks and regards,

    -George

  • 0 in reply to George Mock
    Expert 1495 points

    The trouble with this file (for release 6.1.0) is that it is now 2 1/2 years old, so does not include any defects identified since the date the compiler release was made available.  Hence my original post.  I know there are more defects, as one of my colleagues found one only a couple of months ago.  Clearly we don't know about others found elsewhere.

    Regards, Giles

  • 0 in reply to Giles Robnson
    TI__Guru**** 249900 points

    Please go back to the C2000 compiler downloads page.  Look at the Defect History links for the latest versions of the 6.1.x and 6.2.x compilers.  Those two files list out every defect fixed or found since 6.1.0 was released.

    Thanks and regards,

    -George

  • 0 in reply to George Mock
    Expert 1495 points

    That certainly provides more information, at least for the fixed defects, but those under “Current Known Issues” don’t say in which releases they are present.  For example, SDSCM00050131 is an issue in releases 6.1.10 and 6.2.9, but was it also present in 6.1.0?

    Also, I find that SDSCM00047849 is a Known Issue in 6.1.0, but not mentioned in the histories for 6.1.10 and 6.2.9.  This does not affect us when using 6.1.0, but it looks like this issue has got overlooked in the later releases.

    Regards,
    Giles

  • 0 in reply to Giles Robnson
    TI__Guru**** 249900 points

    Giles Robnson said:
    SDSCM00050131 is an issue in releases 6.1.10 and 6.2.9, but was it also present in 6.1.0?

    The known issues list for a given release shows the known bugs as of the date of that release.  This bug was discovered after the release of 6.1.0, thus it does not appear on the 6.1.0 known issues list.

    Giles Robnson said:
    I find that SDSCM00047849 is a Known Issue in 6.1.0, but not mentioned in the histories for 6.1.10 and 6.2.9.

    I see this issue in the 6.1.10 defect history.  It is not listed in 6.2.9 because it is not present in that release.  In fact, it is not present in any 6.2.x release.

    Thanks and regards,

    -George

  • 0 in reply to George Mock
    Expert 1495 points

    George Mock said:

    SDSCM00050131 is an issue in releases 6.1.10 and 6.2.9, but was it also present in 6.1.0?

    The known issues list for a given release shows the known bugs as of the date of that release.  This bug was discovered after the release of 6.1.0, thus it does not appear on the 6.1.0 known issues list.

    [/quote]

    Which takes me back to my first question, how do I get a list of all defects on release 6.1.0, those that were known at the time of release, and those that have been discovered later.

    George Mock said:

    I find that SDSCM00047849 is a Known Issue in 6.1.0, but not mentioned in the histories for 6.1.10 and 6.2.9.

    I see this issue in the 6.1.10 defect history.  It is not listed in 6.2.9 because it is not present in that release.  In fact, it is not present in any 6.2.x release.

    [/quote]

    But earlier reply implied that fixed defects were listed against later releases when they were fixed, though this now implies that this is not the case.

    I don't feel I'm asking anything unusual here.  We are writing safety-critical code and one of  the verification requirements we have to fulfil is to show that all known compiler defects have been considered, and remedial action taken if needed.  That's all known defects, not just those known about 2 years ago.

    If I could get access to the Defects database (see original post), would I be able to query for this?

    Regards, Giles

  • 0 in reply to Giles Robnson
    TI__Intellectual 2010 points

    Giles,

    In the DefectHistory.txt:

    Defects that are fixed are reported against the first release in which the defect is fixed.   In the Release Notes for the fix, there is often a sentence that indicates which releases contain the defect. 

    Accessing ClearQuest for the known issues would only show you at best a particular release that contains the defect for each ClearQuest entry.  What I assume you would want to see is all the releases that contain the defect.   In general, a known defect typically affects every release on that branch.   It would be fair to make that assumption about the known defects.

    The DefectHistory.txt for C2000 6.1.10 provides the latest information for defects on a particular branch (ex. C2000 6.1.x). 

    -Mack

  • 0 in reply to mjoyner
    Expert 1495 points

    OK.  That's what I need to know.

    Thanks
    Giles