Hi,
This question can be divided into two parts:
1) How well do Vision SDK handle compiler flags for optimization? Is there any flag that should be avoided?
2) Which flags are recommended?
Regards
Erik
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.
Hi Erik,
Each CPU has its own compiler and each compiler uses different compilation flags.
Please see PROCESSOR_SDK_VISION_03_07_00_00\vision_sdk\build\rtos\makerules\rules_<arch>.mk.
Optimization flags begin with -O'x' where x denotes optimization level.
You can refer to compiler documentation and help for more information.
Regards,
Rishabh
Hi Rishabh,
Thanks for the information. But I got a follow up question on this topic:
In the file "PROCESSOR_SDK_VISION_03_07_00_00\vision_sdk\build\rtos\makerules\rules_m4.mk", I can see that:
- debug it is built without optimization
- release is built with -O3 --optimize_with_debug, and I can understand that in some cases you would like to have debug information
- prod_release is also built with -O3 --optimize_with_debug, and I really don't see the reason why you would like to have debug information in your production code. Is this perhaps a copy-paste error?
Regards
Erik
Hi Erik,
--optimize_with_debug is an old flag. It no longer does anything.
http://software-dl.ti.com/ccs/esd/documents/sdto_cgt_debug_versus_optimization_tradeoff.html
Also we are not building/testing prod_release. You can ignore it.
Regards,
Rishabh
Hi,
I haven't heard back from you, I'm assuming you were able to resolve your issue.
If not, just post a reply below (or create a new thread if the thread has locked due to time-out).
Regards,
Rishabh