CCS/MSP430F6736: XDCTools Bug List

Ralph,
there is no a tool that would give you a list of bugs that were open at the time a particular version of XDCtools was released, but you can find some of it from the Eclipse database. It does require some advancing searching. For example, here is the list of bugs that were detected in releases before 3.32.00, and then closed before Feb 2016, which is approximately when XDCtools 3.32 was released (see here http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/rtsc/3_32_00_06/index_FDS.html):

https://bugs.eclipse.org/bugs/buglist.cgi?chfield=bug_status&chfieldfrom=1998-07-01&chfieldto=2016-02-02&chfieldvalue=CLOSED&classification=Technology&list_id=19706580&product=RTSC&query_format=advanced&version=3.25.7&version=3.30.0&version=3.30.1&version=3.30.6&version=3.31.0

Also, you can find which bugs were fixed in a particular version of XDCtools. Here is the search for XDCtools 3.32.00:

I am also curious how did you find that info for compilers. I know some of the bugs are listed in the release notes, but I don't think there is a u public database for all compiler bugs. 

I will ask around if anyone at TI has a better idea what we can do for customers with safety critical requirements.

I know that thread below doesn't answer the question asked here, but it might be useful for anyone developing safety-critical code with TI-RTOS:

https://e2e.ti.com/support/legacy_forums/embedded/tirtos/f/355/p/559748/2051529

https://e2e.ti.com/support/legacy_forums/embedded/tirtos/f/355/p/313154/2043850

Sasha,

Thank you for the additional information. 

With regard to the second link which mentions the availability of SYS/BIOS test results, how would I access these test results for SYS/BIOS v6.46.00.23 specifically?

For the compiler bugs, I made a note of the URL that I used to get the bug list, which was indirectly through a forum link somewhere (which I didn't keep, unfortunately.)  After I followed the forum link, the interface allowed me to adjust the query for the bug list until I got all of the items I needed for specific versions of the tools.  The URL that resulted was this:

https://cqweb.ext.ti.com/cqweb/#/SDO-Web/SDOWP/QUERY/38073958&format=HTML&noframes=false&format=HTML&version=cqwj

Which I now see I no longer can access directly.  So why wouldn't this bug list be publicly available?

Thanks again.

I can't really tell from the link what are the search conditions, but you need to find out all bugs that are filed before a specific date AND were not fixed before that date. You don't want to miss ones that are fixed after 3.32.06. You will also have many xgconf and ROV bugs in that list, and they are mostly likely not relevant to you in the likely case that you don't used xgconf. ROV is a debugger, and the ROV bugs do not affect safety of your code.

My XDCTools buglist search parameters were the following:

product=RTSC

bug_status=ASSIGNED or NEW

status changed (which I expect would include newly created ones) from 1998-07-01 to 2015-12-02

I can see how this query would miss items that are closed but were closed AFTER the version we are using (were not fixed before release date of 3.32.06.)

https://bugs.eclipse.org/bugs/buglist.cgi?bug_status=ASSIGNED&bug_status=NEW&chfieldfrom=1998-07-01&chfieldto=2015-12-02&chfieldvalue=ASSIGNED&classification=Technology&product=RTSC&query_format=advanced

I suppose I need two queries.  The above one, and another which is bugs closed after Dec 2015, but filed before that.

I'm not sure how to formulate the second query, as the query URL I'm manipulating seems to allow a date for the change of status but I don't see how to ask that it changed to closed (and not get new bugs filed after the release date.)

Any ideas?

You can see an option for exporting to CSV files at the bottom of the page with results. I think I would try to use that to find bugs that are closed after the release date, but were not filed after the release date.

So, you search for ones that are closed after, and then use the result of the search for the bugs filed after the release date to filter results of the first search.