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.

Combine DEBUG and RELEASE BUILDS



I have a project the builds in debugging mode, but not release mode for the C674x target, and builds in both release and debug mode for C667x. There are thousands of files in the project, and it only fails in five functions in one specific file. All these functions do is read/write a structure and do lots and lots of double multiplications and additions/subtractions, but nothing else. 

There is very little to optimize there.

Is there a way for me to run this specific file not in release mode, and the rest of the project in release mode. 

Thank you.

  • Yaels Steinsaltz,

    "Thousands of files" is a lot. Is this an exaggeration?

    If the project does not build in Release Configuration, there would be warnings and/or errors posted by the compiler/linker. What are those messages?

    With the Release Configuration active, you can select the file in question, right-click on it in the Project Window and select Properties. In the properties dialog, you can change the compiler options for that file while leaving the other files with the default build properties for the Release Configuration. Try adding -g, then try reducing the optimization one step at a time instead of removing optimization completely.

    Regards,
    RandyP

  • It hangs, therefore no errors or warnings posted. 

    Thousands of files is the entire code base of our group, so not an exaggeration.

    We are not using CCSv5 for build, we have a make system. so no project window or properties button, what would be the command line to change in the makefile of this directory to build this file differently from the others? 

  • Yaeis,

    CCSv5 has the hooks to do this. If you are writing your own makefile, then you will have to edit the makefile to change how is builds the object file for this source file.

    You asked this question on the hardware-oriented C67x Single Core DSP Forum. It should have been posted to the Compiler Forum where they know more about software tools, but they may not support external custom makefiles since they offer CCS to do the job for you. I will ask a Moderator to move this thread there for your convenience, although they may send you to the Code Composer Forum; I do not know.

    Your makefile executes a build step for each file. A set of compiler options are used there to implement the differences between Debug and Release Configurations. If you want to customize that, you will have to do that by editing the makefile.

    Regards
    RandyP

  • CCS only builds for TI, and not easily even when moving between TI platforms (6437, 6455, 6740, 6672, etc.), a make environment can build for all our platforms (including PC). What I can use is a specific make instruction to default to DEBUG build mode for the 674x platform, for one specific file.

    When I break after the compilation hangs the following message appears:

     INTERNAL ERROR: C:\ti\ccsv5\tools\compiler\c6000_7.3.17\bin\cg6x.exe experienced a fatal internal fault

    This is a serious problem. Please contact Customer
    Support with this message and a copy of the input file

  • Yaels Steinsaltz said:

    When I break after the compilation hangs the following message appears:

     INTERNAL ERROR: C:\ti\ccsv5\tools\compiler\c6000_7.3.17\bin\cg6x.exe experienced a fatal internal fault

    Does this happen consistently, or only when you manually stop the build with ctrl-C?  If it is consistent, then I'd appreciate if you would send us a test case.  Please preprocess the code (that link includes a description of how to do it from a make file) and submit it.  Please include the exact build options used.

    Thanks and regards,

    -George

  • Until this was moved from the apparently wrong location I originally posted on, it has been dealt with and determined to be a bug reported in  SDSCM00050725 for tracking. 

    Thank you, 

    Yael