CCS/TM4C129ENCPDT: Compiler differences between Linux and Windows

Russell Jackson

Part Number: TM4C129ENCPDT

Tool/software: Code Composer Studio

Hello,

I have been trying to port some of embedded programs from windows development to linux development. Unfortunately, even though I am using all of the same libraries and compilers. The ndk library I use has some differences when it is compiled in Windows Vs Linux. I am trying to understand why this difference exists, its significance, and finally if I can remove it so that the files are functionally the same. An example difference is in the stk_nat_ppp_pppoe file. By comparing the files using objdiff from cgxml-2.61.00, I get the following difference:

objdiff linux\stk_nat_ppp_pppoe.aem4f windows\stk_nat_ppp_pppoe.aem4f ofd6x
Processing linux\stk_nat_ppp_pppoe.aem4f ...
Processing windows\stk_nat_ppp_pppoe.aem4f ...
Comparing files ...

**********************************************************************
Filename sock.oem4f
**********************************************************************
======================================================================
Comparing Sections : section = .text:SockShutdown : elf32_shdr
======================================================================
Differences: linux\stk_nat_ppp_pppoe_02.aem4f windows\stk_nat_ppp_pppoe.aem4f
sh_size: 0x70 0x7c

Files are different

For reference, here is the relevant tool-chain information:

Target: ti.targets.arm.elf.M4F

Compiler: ti-cgt-arm_5.2.6

XDC tools: xdctools_3_31_01_33_core

SYSBIO version: bios_6_42_03_35

over 7 years ago

0 George Mock over 7 years ago

TI__Guru**** 251550 points

That diagnostic from objdiff means the function SockShutdown from the file sock.c is 0x70 bytes when built on Linux, and 0x7c bytes when built on Windows. To understand this better, build sock.c as before, but add the option --src_interlist. This causes the compiler to keep the generated assembly file, and to add comments which make it easier to understand. Inspect the two assembly files. The difference may be apparent. If not, you should be able to ask more focused questions about the difference.

Thanks and regards,

-George

0 George Mock over 7 years ago

TI__Guru**** 251550 points

Russell Jackson said:
Compiler: ti-cgt-arm_5.2.6

That compiler is almost 3 years old. Please consider an upgrade.

Thanks and regards,

-George

0 Russell Jackson over 7 years ago in reply to George Mock

Prodigy 90 points

Hello George,

Thank you for your suggestions. Unfortunately we have to use the ti-cgt-arm_5.2.6 to support our legacy software products.

Based on the objdiff output, A colleague of mine discovered that there are actually differences in the linux and windows source code of the ndk library. Is there a reason for the difference and should it be possible to simply replace the source code to ensure that the files match? Please see the differences in the attached image.

Thank you

-Russell

0 ToddMullanix over 7 years ago in reply to Russell Jackson

TI__Guru* 96960 points

What version of the NDK are you using?

0 Russell Jackson over 7 years ago in reply to ToddMullanix

Prodigy 90 points

Hi,

We are using ndk 2.24.03.35 . I hope this helps

-Russell

0 ToddMullanix over 7 years ago in reply to Russell Jackson

TI__Guru* 96960 points

Hi Russell,

That line is not in the NDK. We ship a zip for the NDK, so there is no Linux vs Windows version. It looks like someone added that line per: e2e.ti.com/.../487729 for one of your installs.

Todd

0 Russell Jackson over 7 years ago in reply to ToddMullanix

Prodigy 90 points

Todd,

Thank you for the information. It answered my question.

-Russell

Code Composer Studio™︎

Code Composer Studio forum

CCS/TM4C129ENCPDT: Compiler differences between Linux and Windows