#27010-D Not all available code size is being used. Recommend running Optimization Assistant to find best speed vs size setting (--opt_for_speed). Double-click to start.
A successful link using a low setting for --opt_for_speed indicates that there may be sufficient memory available to allow increasing the --opt_for_speed setting for additional performance improvements.
The option --opt_for_speed controls the tradeoff between size and speed (0-5 range). Setting --opt_for_speed=0 enables optimizations geared towards improving code size with a high risk of worsening or impacting performance. At the other extreme, setting --opt_for_speed=5 eanbles optimizations geared towards improving the code performance/speed with a high risk of worsening or impacting code size. Settings between 0 and 5 vary the emphasis on performance versus code size.
Use the Optimizer Assistant feature to build your project for all settings of --opt_for_speed. You can either double click on the Advice View entry, or select menu View->Other->Code Composer Studio->Optimizer Assistant.
You will see below (or click on green play button to start).
Select "speed vs. size trade-offs" (or you can select to vary by optimization level), and CCS will build your project with all settings for selected option to vary.
The results window will update during the build run.
Final results will show a bar chart of code size for each --opt_for_speed setting. Any builds that failed link will show in red. In below results window, the green check mark represents current setting for --opt_for_speed, and the green bar is recommended setting.
Hovering the cursor over a bar will present options to update project settings or to debug the program.
Additional performance improvements may be possible when using higher settings for --opt_for_speed.
Run the Optimizer Assistant to generate data for code size versus
--opt_for_speed setting.