just pulled down v4.5.2 of the TI arm compiler, and built some reference applications using --abi=eabi (ELF) and --abi=ti_arm9_abi (COFF).... in general, the .text section of the eabi (ELF) version is about 10% larger; looking at the sizes of individual functions reported in the linker map confirms this.... here's a snip from an ELF map....
.text 0 00000000 00000978 00000000 00000383 App_xv7M3-TI-E.ov7M3-TI-E (.text:xdc_runtime_System_doPrint__I) 00000383 00000001 --HOLE-- [fill = 0] 00000384 000000e8 App_xv7M3-TI-E.ov7M3-TI-E (.text:xdc_runtime_Startup_startMods__I) 0000046c 000000d4 App_xv7M3-TI-E.ov7M3-TI-E (.text:xdc_runtime_System_printfExtend__I)
and here's the corresponding snip from the COFF map....
.text 0 00000000 00000896 00000000 0000032f App_xv7M3-TI-C.ov7M3-TI-C (.text:_xdc_runtime_System_doPrint__I) 0000032f 00000001 --HOLE-- [fill = 0] 00000330 000000e8 App_xv7M3-TI-C.ov7M3-TI-C (.text:_xdc_runtime_Startup_startMods__I) 00000418 000000bc App_xv7M3-TI-C.ov7M3-TI-C (.text:_xdc_runtime_System_printfExtend__I)
while some functions show no change in size, others show quite a bit of growth....
is there something in the eabi spec (versus the TI arm9_abi) that accounts for this growth in program size on a per-function basis??? note that in both cases, i'm using conditional linking to eliminating unreferenced functions; the problem is that the functions which remain are somewhat larger.... otherwise, the options used to build these applications are identical in the ELF vs COFF cases
has anyone else observed this using the TI arm compiler???
We are aware of one issue. When the compiler calls a built-in function (such as I$MOD, which is used to compute %), does it know which registers are modified by that function? Under TI_ARM9_ABI, it does. Under EABI, it doesn't. That is because there is no guarantee that the TI EABI RTS library gets used. Some other EABI compliant ARM library could supply that function. The compiler has to be conservative and presume that all registers, except the few registers the calling convention requires be saved by a function, are modified. And this presumption has negative consequences on how registers get used generally, which increases memory accesses and code size.
Thanks and regards,
TI C/C++ Compiler Forum ModeratorPlease click Verify Answer on the best reply to your question.The Compiler Wiki answers most common questions.Track an issue with SDOWP. Enter your bug id in the "Find Record ID" box.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.