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.

Optimization Compiler Problems?



hello everyone:

I have a question, I read the TMS320C6000 Optimizing Compiler v 6.1 SPRU187O this document, in which 3.5 Reducing Code Size (- opt_for_space (or-ms) Option) in the

compiler option is set to get smaller the higher the level of the Code Size, I used the example you provide "dvsdk_1_01_00_15 \ examples \ video_preview" to do tests results

are as follows:

none ms0 ms1 ms2 ms3
none 146784 146528 146560 146496 146432
o0 146912 146496 146592 146400 146368
o1 146720 146560 146560 146304 146272
o2 146624 146560 146560 146240 146240
o3 146624 156528 146560 146272 146240

In theory it should be dropped, but why increase cases,
My other settings are the same Target Version             :  C64x +
                                                        
Generate Debug Info  :  No Debug

Menu, select "Collect Application Level Profile for Total Cycles and Code Size"

Use: Tuning -> Goals Views

 

  • Generally, everything is moving smalled as would be expected, but there are a couple of non-linearity points that are not quickly explained.

    Usually with C code, there is a very distinct change from no optimization to -o0 and other levels of optimization. The fact that you are not seeing this distinct change makes me think there is something unique about the files you are optimizing that leads to these results.

    Rather than digging into why these results are seen, I would ask that you examine your goals for this project and the requirements that you have. If you find that answer to "why increase cases" is vital to your success, then you may want to move this posting to the "Development tools" forum which is more closely monitored by the development tools team.