• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 53 subscribers
  • Views 344 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.

CCS/AWR1843: Issue with Flexelint errors

Matteo Sticco
Prodigy 90 points
Part Number: AWR1843

Tool/software: Code Composer Studio

Hi,
I am working on a project at my company and our code must be MISRA compliant. However it seems that some intrinsics cannot be seen by Flexelint so we get a lot of errors belonging to rules 8.3 and 8.4.
Can someone please suggest where are the headers files containing the intrinsics prototypes so that we can set this (or these) path(s) in Flexelint in order to reduce the number of errors?
Thanks and regards
  • 0
    TI__Guru**** 249900 points

    Your device has both ARM and C6000 CPU cores on it.  I'll answer for both compilers.  For the TI ARM compiler #include <arm_acle.h>.  For the C6000 compiler, #include <c6x.h>.  That will provide a function prototype for most of the intrinsics.  That said, these include files are not tested to solve your particular problem, so you might encounter some gaps.

    Thanks and regards,

    -George

  • 0 in reply to George Mock
    Prodigy 90 points

    Thanks for your reply.

    We had a look at those files but we didn't find some intrinsics prototype, e.g. _amemd8.

    Is it possible that some other .h files are generated at compile time and so they're not really accessible before?

    Thanks again for your support,

    Matteo

  • 0 in reply to Matteo Sticco
    TI__Guru**** 249900 points

    Unfortunately, those header files are the best solution we have for your particular problem.  

    Matteo Sticco said:
    Is it possible that some other .h files are generated at compile time and so they're not really accessible before?

    Unfortunately, no.

    Thanks and regards,

    -George

  • 0 in reply to George Mock
    Prodigy 90 points

    Hello,

    I think I resolved the issue.

    I created an header file containing the prototypes of the intrinsics I needed and I used a #define in order to prevent the compiler to see them. At the same time this #define is added to the configuration file of flexelint to let it recognize them.

    Hope this will help anyone who has the same problem!

    Regards,

    Matte Sticco