• Locked Locked
  • Replies 2 replies
  • Subscribers 55 subscribers
  • Views 575 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.

TI compiler tested and conform with ISO/IEC C standards?

grizzly
Intellectual 1665 points


Hallo,

a medical customer is having a question if our Compiler (which are used with CCS) are validated against ISO/ICE standard like e.g done for IAR.

Could you please let me know if TI is also doing similar approach?

Best Regards, Christine

Customer wrote:

I was interested in any information which could help to prove that TI compiler is suitable for
development of medical applications. This could be proof of conformance
to the standards. For example IAR Systems uses the following commercial
test suites to test their compiler:

   * Plum Hall Validation test suite for ISO/IEC C conformance
   * Perennial EC++VS (Embedded C++ validation suite) for Embedded C++
     conformance
   * Dinkum C++ Proofer to test how our libraries conform to the C and
     Embedded C++ standard as well as test our STL implementation
     against the C++ standard.

Is there any information you could provide about how TI compiler is
tested against ISO/IEC C standard? Or against which standard is TI
compiler tested?

  • in reply to George Mock
    TI__Guru*** 125430 points

    Unfortunately it's not entirely true about our C89 compliance.  Specifically, we fail to initialize any uninitialized global variables to 0 as required by the standard.  Specifically, if you declare a global/static variable such as:

    int g_var;

    it will not receive any initialization value even though ANSI C dictates the above variable must be initialized to zero.  So while I would say we are mostly ANSI compliant this is at least one case I know of that we are not.

    Are there any other known issues like the one above?  If so, I recommend documenting them on the wiki page listed by George.

    Also, I hear we're supposed to be correcting this issue in some of the upcoming tools.  Maybe some from CG team can further comment.  I don't know all the details such as whether only c6000 will get the enhancement or if it will be everybody, nor do I know the timeline.  That might be another good bullet for the wiki...