• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 101 subscribers
  • Views 253 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.

TDA4VH-Q1: Using gcc or clang vs TI clang

Jason White
Prodigy 70 points
Part Number: TDA4VH-Q1

Tool/software:

We are thinking of using the open source versions of gcc or clang for our project instead of the TI Clang version for building R5 content..  Are there any risks using the open source versions especially dealing with the TI sdk/drivers for the R5?  My understanding is the only change is with the linker to reduce code size based on the link below.  Code size is not critical for us, but long term support and new compiler features are.  Is there anything in the TI drivers that uses non-compliant C code?  I wouldn't think so.

https://www.ti.com/document-viewer/lit/html/SSZT210

Thanks

  • 0
    TI__Guru**** 249900 points
    Jason White said:
    Code size is not critical for us, but long term support and new compiler features are

    With regard to long term support and new compiler features, do not expect a big difference between tiarmclang and ...

    Jason White said:
    open source versions of gcc or clang

    For additional information, please see the C Language Extensions part of the tiarmclang online manual.

    Jason White said:
    Are there any risks using the open source versions especially dealing with the TI sdk/drivers for the R5?

    For the answer to this question, I changed the responsibility for this thread to the team that supports the SDK.

    Thanks and regards,

    -George

  • 0 in reply to George Mock
    TI__Guru** 112775 points

    Hi Jason,

    The TI SDK source code and all of our validation is done with TI ARM Clang Compilers only (we used to use a different TI ARM Code Generation Tool Compiler on older SDKs).

    TI expects the customers to own any needed changes required to use with a different compiler, and TI cannot guarantee that the SDK code will compile out-of-box with a different compiler.

    The TI ARM CLANG Usage and Migration Guidelines section of the PDK documentation has documented some of the pitfalls during our migration from TI ARM CGT to TI ARM Clang, and expect somewhat similar issues with other public different Compilers. The differences will be smaller with clang compiler versus some of the other publicly available ARM Compilers.

    The A72-side keeps on moving to a newer ARM GCC Compiler for every major SDK release.

    The SDKs also are not fixated on a particular TI ARM Clang Compiler release, and we do tend to move to a newer Compiler version from time to time.

    regards

    Suman