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.

Compiler/AWR1443: Executable increases by 4 bytes every time I rebuild, even when nothing changes

Part Number: AWR1443


Tool/software: TI C/C++ Compiler

Problem in the title - every time I rebuild, the binary increases by exactly 4 bytes. Is there a linker or compiler flag that would cause this? It's happening on a slighty modified version of the:

Power Optimized Level Sensing Demo Software (Rev. A) (ZIP, 3237KB)   543 views, 10 Jan 2018

where the topRange function has been replaced with a nearly equivalent C-wrapped C++ function, and I'm using XDC 3.50.5.12, SYS/BIOS 6.53.2.0

  • Alex Shirley said:
    the binary increases by exactly 4 bytes.

    I presume you mean the binary executable object file produced by the linker.  It often has the file extension .out, but not always.

    My guess is that the amount of target system memory used does not change.  An easy way to check ... Inspect the map file created by the linker.  Look for the MODULE SUMMARY.  Does the Grand Total at the end change between builds?  I suspect not.  If the target memory used does not change, then the change is in the debug information, or other meta-information, in the object file.

    Alex Shirley said:
    Is there a linker or compiler flag that would cause this?

    No

    Thanks and regards,

    -George