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.

TMS320C6748: Release mode versus Debug mode size indicates debug data is not compiled out

Part Number: TMS320C6748

Code Composure 10.4: If I can build in Release mode and also build in Debug mode, why is the Release .out file bigger?  The Debug mode .out file is 5,263,136 bytes, and the Release mode .out file is 5,271,972 bytes.  I thought Release mode would be smaller, and I can still debug with the Release build.  What am I missing?

Thank you for the help.

  • Hello Marsha,

    The size of the .out file depends on the compiler settings. You'll need to check the compiler settings for both release and debug builds.

    Let me loop in our compiler team for further help.

    Regards,

    Jianzhong

  • I thought Release mode would be smaller, and I can still debug with the Release build.  What am I missing?

    There are a few things to consider:

    Note that "Debug" and "Release" are simply default build configurations. Build configurations are just a set of options passed to the compiler, and there are no strict rules for what options should be used for "Debug" or "Release". Different examples can have different implementations. You are correct that *typically*, "Debug" results a bigger code size since full debug symbols is typically generated. But again, it can be variable.

    Also note that an *.out file consists of the actual code binary that is loaded on the target AND the debug symbols that is loaded to the debugger on the host. So it is quite possible to have an *.out file that is overall larger in size but the code binary is smaller because there is additional debug information.

    It is best to check the build options as Jianzhong mentioned and compare the ones for "Debug" and "Release".

    Thanks

    ki