CCS: Optimizer assistant does not change build options

I am trying this out in CCSv8.2 and it is working as expected for me.

I run it and get the graph showing the results for the various options.

I then select the one I want and it gives me the option to apply it to my current build configuration.

Here I have selected "Apply this setting to 'Debug' ".  And I can verify that this was applied to the Debug build configuration as in my case it was trading off performance vs size and I selected bar on the graph that mapped to setting -mf to 3

Are you selecting to apply the changes you your project?  If you are and that is not happening is the project checked out?  i.e. is it in source control and checked out for writing?

Regards,

John

All the entries in the chart are the same when I run it. I have not tried the "apply this setting" option. I actually don't recall ever seeing it, although it probably is there. The project is writable and I'm using the Windows version of CCS.

If it is a small application it is pretty typical for there not to be much or any difference between the settings. There needs to be code in the application where there is a trade-off to be made for size vs speed (unrolling...). The apply this setting option shows up when you click on one of the bars in the graph. If you don't apply the setting to the project then it is not going to change your project build options.

Regards,
John

I'm actually targeting the optimization level option, but the size vs speed one doesn't work either. The assistant produces identical sizes down to the byte at all 6 optimization levels, but there is a significant difference when I manually change it. From the build console I can see that it's passing only the original value to the compiler for every variation.

I just tried the apply option and it successfully modified my build configuration. So it looks like the assistant does know how to change the optimization level; it's just not doing it when producing the variations. After using apply, the assistant still gives the same size at every level, although that number is smaller than before, corresponding with the increased optimization level.