• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 52 subscribers
  • Views 2637 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CCS5 compilation time ~5times what CCS4 was

jimj2713
Expert 2365 points
Other Parts Discussed in Thread: CCSTUDIO

I recently moved all of my projects from CCS4 to CCS5, and all of these projects are roughly the same number of LOC. In all cases, the CCS4 compilation time was ~30 seconds, and now on CCS5 it is ~3 minutes. I have experimented with different project creation schemes (copying into workspace or not), new project versus import, optimization levels, syntax checks, pre-processing options, and have made to real difference.

The one observation I have, which may help someone guide me, is in CCS5 the Console window states "Invoking: C2000 Compiler" for EVERY C file (~40 times). In CCS4, the compile was only invoked maybe 5 times -- and in both of these cases the build was a clean-build.

I believe the project settings between the CCS4 and CCS5 projects are the same. Any comments or suggestions will be appreciated.

  • 0
    TI__Guru**** 173310 points

    jimj2713 said:
    I recently moved all of my projects from CCS4 to CCS5, and all of these projects are roughly the same number of LOC. In all cases, the CCS4 compilation time was ~30 seconds, and now on CCS5 it is ~3 minutes.

    It would be helpful to have a few more details here.

    1) What is the version of compiler tools being used in the 2 cases? You should be able to see the version by going into Project Properties->General->Advanced Settings->Compiler version

    2) Can you compare the build output in the CCS console view for CCSv4 and CCSv5 and see if there is any difference at all in the options? It might even be helpful if you could copy and paste the outputs in both cases to a text file and attach it here.

    jimj2713 said:

    The one observation I have, which may help someone guide me, is in CCS5 the Console window states "Invoking: C2000 Compiler" for EVERY C file (~40 times). In CCS4, the compile was only invoked maybe 5 times -- and in both of these cases the build was a clean-build.

    This statement makes me wonder if you have the compiler option "--program_level_compile" (-pm) turned on in CCSv4 but not in CCSv5. Could you check if this may be the case?

    3) If you look at the console view during the build, is there a particular place that it stalls for a long time in CCSv5, or is the build time just distributed among the ~40 source files?

  • 0 in reply to AartiG
    Expert 2365 points

    The compiler versions -- in the CCS5 project: TI v6.0.2. In the CCS4 project: TI v6.0.1

    Regarding compiler options, I have compared them, and while these are not identical, I have not found any significant speed improvements on the CCS5 side by changing any of these.

    Here are the CCS4 compiler settings:

    -v28 -ml -g -O3 --program_level_compile --define="_DEBUG" --define="LARGE_MODEL" --include_path="C:/CCStudio_v4.2/ccsv4/tools/compiler/c2000/include" --include_path="C:/CCStudio_v4.2/xdais_7_10_00_06/packages/ti/xdais" --diag_warning=225 --float_support=fpu32 --call_assumptions=0 --auto_inline=30 --c_src_interlist --asm_listing --asm_directory="C:/Software/UnifiedCCS4/Asm" --obj_directory="C:/Software/UnifiedCCS4/Debug" --list_directory="C:/Software/UnifiedCCS4/List"

    And the CCS5 compiler settings:

    -v28 -ml --float_support=fpu32 -O3 -g --include_path="C:/CCStudio_v5/ccsv5/tools/compiler/c2000/include" --define=_DEBUG --define=LARGE_MODEL --diag_warning=225 --call_assumptions=0 --c_src_interlist --asm_listing

    I did try --program_level_compile in the CCS5 project, and while it does speed up compilation, the application fails to link. Maybe this is the real problem? With --program_level_compile, CCS5 reports cannot find file assert.obj, which is of course locatable without --program_level_compile. I could not resolve this issue; why would program_level_compile affect linker file location?

    Note to your last question, the compilation delays are evenly distributed amoung the files -- it just takes longer for each file in this CCS5 project.

    Thanks.

  • 0 in reply to jimj2713
    TI__Guru**** 173310 points

    The --program_level_compile option could very well contribute to the difference in compile time. It certainly does explain your earlier statement that in CCSv5, it invokes the compiler for every C file (~40 times) while in CCSv4, it was invoked about 5 times.

    When program_level_compile is enabled, all the C source files are passed together to the compiler shell in one step and the compiler creates a single module out of all the C source files and then builds that module.

    jimj2713 said:

    I did try --program_level_compile in the CCS5 project, and while it does speed up compilation, the application fails to link. Maybe this is the real problem? With --program_level_compile, CCS5 reports cannot find file assert.obj, which is of course locatable without --program_level_compile. I could not resolve this issue; why would program_level_compile affect linker file location?

    This is interesting, but if we can get the link issue resolved I think you will see the speedup in build time. Do you have the --obj_directory option in your CCSv5 build as well? I don't see it in your snippet above, but if you do have that set, can you remove the directory specification (so it goes into the default location) and then clean and rebuild and see if that helps?

    If it does not help, can you share your project so we can reproduce this link issue and look into it? That would be the quickest way to move forward. If you cannot share your project, can you copy and paste the full output from the CCS build console to a text file and attach it there? Also a screenshot of your Project Explorer view that shows all the expanded view of your project (so all source files are visible) would help. We'll try to see if we can figure out what is going on starting with that information.

  • 0 in reply to AartiG
    Expert 2365 points

    I did not have the --obj_directory option set; it did not occur to me that those directory options would be relevant here -- it's funny that would have to be set, when the compiler itself is creating the object files it cannot find.I added the --obj_directory option, and it had no effect.

    I would like to see if we can fix this without sharing the full source, so here is the compiler output. I don't know if this is important, but look at the "cannot find" error statement near the end: "C:\\Users\\DCABAL~1\\AppData\\Local\\Temp\\079363", line 23: error: cannot find file "./ASSERT.obj" -- is it possible it is "./Assert.obj" is relative to ""C:\\Users\\DCABAL~1\\AppData\\Local\\Temp\\079363"?

    Another observation: in the top-program-level compilation statement, assert.c is near the end of the list -- could this be a compilation-order issue?

    Lastly, near the end of this console-output, there is a statement "Finished building: ASSERT.obj", and that is the only obj mentioned -- what is that?

    I also attached the console output of a good (but slow) compilation of this same project, if that helps.

    Thanks again.

    4265.ProgramLevelCompileLinkError.txt
    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    **** Build of configuration Debug for project Unified ****
    C:\CCStudio_v5\ccsv5\utils\bin\gmake all
    'Invoking: C2000 Compiler'
    "C:/CCStudio_v5/ccsv5/tools/compiler/c2000/bin/cl2000" -v28 -ml --float_support=fpu32 -O3 -g --include_path="C:/CCStudio_v5/ccsv5/tools/compiler/c2000/include" --program_level_compile --define=_DEBUG --define=LARGE_MODEL --diag_warning=225 --call_assumptions=0 --c_src_interlist --asm_listing --obj_directory="C:/Software/Unified/Debug" "../24FC128.c" "../AD9835.c" "../AE_IO.c" "../Bit.c" "../Buffer.c" "../CAN.c" "../Constants.c" "../Control.c" "../Customer.c" "../DSP2833x_Adc.c" "../DSP2833x_CpuTimers.c" "../DSP2833x_DMA.c" "../DSP2833x_DefaultIsr.c" "../DSP2833x_ECan.c" "../DSP2833x_ECap.c" "../DSP2833x_EPwm.c" "../DSP2833x_EQep.c" "../DSP2833x_GlobalVariableDefs.c" "../DSP2833x_Gpio.c" "../DSP2833x_I2C.c" "../DSP2833x_Mcbsp.c" "../DSP2833x_MemCopy.c" "../DSP2833x_PieCtrl.c" "../DSP2833x_PieVect.c" "../DSP2833x_Sci.c" "../DSP2833x_Spi.c" "../DSP2833x_SysCtrl.c" "../DSP2833x_Xintf.c" "../Error.c" "../Filter.c" "../FluxReg.c" "../HS_Loop.c" "../Hall.c" "../HiDS.c" "../HiDSMenu.c" "../I2T.c" "../IO.c" "../Induction.c" "../Inrush.c" "../LED.c" "../LS_Loop.c" "../LTC2629.c" "../ManualFeedback.c" "../Overcurrent.c" "../PCA9539.c" "../PidReg.c" "../Power.c" "../RFFT_f32_sincostable_IQ.c" "../RamTest.c" "../Regen.c" "../Resolver.c" "../SelfTest.c" "../Sensorless.c" "../System.c" "../TestPoint.c" "../TestScripts.c" "../Torque.c" "../Utility.c" "../VersionNotes.c" "../Watchdog.c" "../main.c" "../smopos.c" "../terminal.c" "../ASSERT.C" "../DSP2833x_ADC_cal.asm" "../DSP2833x_CSMPasswords.asm" "../DSP2833x_CodeStartBranch.asm" "../DSP2833x_DBGIER.asm" "../DSP2833x_DisInt.asm" "../DSP2833x_usDelay.asm" "../Mac80Iterations.asm" "../RFFT_f32.asm" "../RFFT_f32_mag.asm" "../RFFT_f32_phase.asm" "../RFFT_f32_sincostable_IQ.asm" "../RFFT_f32u.asm" "../atan2_f32.asm" "../atan_f32.asm" "../cos_f32.asm" "../div_f32.asm" "../sin_f32.asm" "../sin_pu_f32.asm" "../sqrt_f32.asm" "../FPUmathTables.ASM"
    [24FC128.c]
    [AD9835.c]
    [AE_IO.c]
    [Bit.c]
    [Buffer.c]
    [CAN.c]
    [Constants.c]
    [Control.c]
    [Customer.c]
    [DSP2833x_Adc.c]
    [DSP2833x_CpuTimers.c]
    [DSP2833x_DMA.c]
    [DSP2833x_DefaultIsr.c]
    [DSP2833x_ECan.c]
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    2671.GoodButLongCompilation.txt
    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    **** Build of configuration Debug for project Unified ****
    C:\CCStudio_v5\ccsv5\utils\bin\gmake all
    subdir_rules.mk:427: warning: overriding commands for target `RFFT_f32_sincostable_IQ.obj'
    subdir_rules.mk:420: warning: ignoring old commands for target `RFFT_f32_sincostable_IQ.obj'
    'Building file: ../24FC128.c'
    'Invoking: C2000 Compiler'
    "C:/CCStudio_v5/ccsv5/tools/compiler/c2000/bin/cl2000" -v28 -ml --float_support=fpu32 -O3 -g --include_path="C:/CCStudio_v5/ccsv5/tools/compiler/c2000/include" --define=_DEBUG --define=LARGE_MODEL --diag_warning=225 --call_assumptions=0 --c_src_interlist --asm_listing --preproc_with_compile --preproc_dependency="24FC128.pp" "../24FC128.c"
    'Finished building: ../24FC128.c'
    ' '
    'Building file: ../AD9835.c'
    'Invoking: C2000 Compiler'
    "C:/CCStudio_v5/ccsv5/tools/compiler/c2000/bin/cl2000" -v28 -ml --float_support=fpu32 -O3 -g --include_path="C:/CCStudio_v5/ccsv5/tools/compiler/c2000/include" --define=_DEBUG --define=LARGE_MODEL --diag_warning=225 --call_assumptions=0 --c_src_interlist --asm_listing --preproc_with_compile --preproc_dependency="AD9835.pp" "../AD9835.c"
    'Finished building: ../AD9835.c'
    ' '
    'Building file: ../AE_IO.c'
    'Invoking: C2000 Compiler'
    "C:/CCStudio_v5/ccsv5/tools/compiler/c2000/bin/cl2000" -v28 -ml --float_support=fpu32 -O3 -g --include_path="C:/CCStudio_v5/ccsv5/tools/compiler/c2000/include" --define=_DEBUG --define=LARGE_MODEL --diag_warning=225 --call_assumptions=0 --c_src_interlist --asm_listing --preproc_with_compile --preproc_dependency="AE_IO.pp" "../AE_IO.c"
    'Finished building: ../AE_IO.c'
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

     

  • 0 in reply to jimj2713
    TI__Guru**** 173310 points

    It looks like CCS is having trouble with the file name ASSERT.C, specifically the extension being in upper case (.C). If you look at the build command, you can see that it is expecting ./ASSERT.obj in the link step, when actually there is probably no ASSERT.obj created in the \Debug folder, but rather a differently named .obj. When compiling with --program_level_compile, there will only be one .obj generated for all C source files combined, since all the C source files are combined into one module and then compiled. CCS 5.1.x seems to have trouble with the .C extension. Try renaming the file to ASSERT.c and see if the build completes. I did a simple test and this workaround helped.

    Also I tried with CCS 5.2 and it was able to handle ASSERT.C fine. So another option might be for you to update to CCS 5.2. You can either update from within CCS5.1 by going to Help->Check for Updates, or you can download and install CCS 5.2.0 in a separate folder.

    Please let us know how it goes.

  • 0 in reply to AartiG
    Expert 2365 points

    That was it -- the capital C in Assert.c; thanks for your help.