In the TI Arm Clang Compiler Tools User's Guide v1.3 the 4.1.8. Library Naming Conventions section appears to be a copy of section 7.1.8 Library Naming Conventions from the ARM Optimizing C/C++ Compiler v20.2.0.LTS User's Guide
However, the TI Arm Clang compiler ti-cgt-armllvm_1.3.0-beta.1 seems to use a different naming convention to that described in the TI Arm Clang Compiler Tools User's Guide v1.3. E.g.
- ti-cgt-armllvm_1.3.0-beta.1 uses the .a suffix for library files, not the .lib suffix described in the User's Guide.
- ti-cgt-armllvm_1.3.0-beta.1 uses separate directories for run time libraries compiled with different options, not the different filename components in the library described in the User's Guide.
Is there a description of how the TI Arm Clang Compiler Library Name Conventions compares to the TI / GCC ARM toolchains?
The reason for asking is was curious to see if the TI Arm Clang provided support for Cortex-R5 big-endian, due to the packaged GCC ARM compilers not containing big-endian run time libraries (e.g. see TMS570LC4357: CCS/TMS570LC4357: compile with ARM compiler 9.3.1)
While the TI Arm Clang Compiler Tools 1.3.0-beta.1 Release Notes shows support for "Cortex-R5 (Thumb) with VFPv3D16", if create a project in CCS 10.3.0 for a TMS570LC4357 and select the ti-cgt-armllvm_1.3.0-beta.1 then fails with an error indicating big-endian targets aren't supported:
Building file: "../main.c"
Invoking: Arm Compiler
"/home/mr_halfword/ti/ccs1030/ccs/tools/compiler/ti-cgt-armllvm_1.3.0-beta.1/bin/tiarmclang" -c -mbig-endian -Og -I"/home/mr_halfword/workspace_v10/TMS570LC4357_TI_CLANG_hello" -I"/home/mr_halfword/ti/ccs1030/ccs/tools/compiler/ti-cgt-armllvm_1.3.0-beta.1/include" -gstrict-dwarf -gdwarf-3 -MMD -MP -MF"main.d_raw" -MT"main.o" -o"main.o" "../main.c"
subdir_rules.mk:7: recipe for target 'main.o' failed
tiarmclang: error: big endian not supported for subtarget.