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.
“Optimizer terminated abnormally” message thrown during compiling of C7x code with -O4 --opt_for_speed=5 command line arguments (there is no problem with --opt_for_speed=1):
Building file: "../v_fix_point_hypot3_test.cpp"
Invoking: C7000 Compiler
"C:/ti/ti-processor-sdk-rtos-j721s2-evm-08_06_00_11/ti-cgt-c7000_3.1.0.LTS/bin/cl7x" -O4 --opt_for_speed=5 --include_path="C:/valeo/workspace/eSmart/v_fix_point_opt_fail" --include_path="C:/ti/ti-processor-sdk-rtos-j721s2-evm-08_06_00_11/ti-cgt-c7000_3.1.0.LTS/include" --diag_warning=225 --diag_wrap=off --display_error_number --preproc_with_compile --preproc_dependency="v_fix_point_hypot3_test.d_raw" "../v_fix_point_hypot3_test.cpp"
>> Compilation failure
subdir_rules.mk:16: recipe for target 'v_fix_point_hypot3_test.obj' failed
>>>> Optimizer terminated abnormally
>>>> in function _ZN10nCore_Math7hypot3dIiLm16ELm16EEENS_11v_fix_pointIT_XT0_EXT1_EEES3_S3_S3_()
>>>> in file "..\v_fix_point_hypot.h"
This is caused by a defect in the TI C/C++ Optimizer.
TI Customer Support may be able to suggest a workaround to avoid this.
Upgrading to the newest version of the compiler may fix this problem.
Contact TI in the E2E support forums at http://e2e.ti.com under
"Development Tools", "TI C/C++ Compiler". See the link titled
"Submitting an issue".
We need to see this ENTIRE error message and a complete, reproducible
test case including ALL of the command-line options.
Include the .pp file created by option --preproc_with_comment
Used compiler is: ti-cgt-c7000_3.1.0.LTS
CCS project generating the internal error is attached.
I’ve found out that the internal error disappears if “non-class” template functions are used instead of static methods of template class. Those options can be switched by changing of "#if 0" at line 28 of v_fix_point_hypot.h to "#if 1".
Thank you for notifying us of this issue, and for submitting a test case. I am able to reproduce the same behavior. I filed the entry EXT_EP-11618 to have this investigated. You are welcome to follow it with that link.
Thanks and regards,
-George