• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 55 subscribers
  • Views 972 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CODECOMPOSER: Code Composer Studio (8, 9, 10) suddenly treats all warnings as errors

Ruediger Casper
Prodigy 205 points
Part Number: CODECOMPOSER
Other Parts Discussed in Thread: AM5726

A few days ago, my CCS 8 started treating all warning messages generated by GCC (GNU v8.3.0 from SDK 6.1) as compile errors. To circumvent this, I always have to build again, because gcc than does nothing ("nothing to do"), so there are no warnings, and CCS continues the build. To fix this, I have already created a new workspace, a clean new copy of the code base, and switched to CCS 9 and 10, but the problem persists. Does anybody have an idea what caused this and how to fix it?

Screenshot:

  • 0
    TI__Guru** 116020 points

    Can you please provide more information for us to help with this issue:

    1. What is the device that you are using?

    2. Can you share the GCC compiler options that you are using. I understand you need to blur the log for proprietary info but we need to understand build option to provide guidance. I am not sure this is caused by CCS as the IDE doesn`t pick compiler options and allows users full flexibility to configure the GCC settings.

    3. Have you compared the compiler flags and compiler version is the same with CCSv8 and CCSv9/10?

  • 0 in reply to Rahul Prabhu
    Prodigy 205 points

    Yes, of course. 

    1) We use the AM5726 with linux rt sdk 6.1

    2) the compiler call is as follows (all paths replaced with [...]):

    Building file: "[...].c"

Invoking: GNU Compiler

"[...]/ti-processor-sdk-linux-rt-am57xx-evm-06.01.00.08/linux-devkit/sysroots/x86_64-arago-linux/usr/bin/arm-linux-gnueabihf-gcc" -c @"[...]/CompilerOptions_ARM_Debug.txt"  -mcpu=cortex-a15 -marm -Dam5726 -Dam5716 -I"[...]/ti-processor-sdk-linux-rt-am57xx-evm-06.01.00.08/linux-devkit/sysroots/x86_64-arago-linux/usr/bin" -I"[...]" -I"[...]/_inc" -I"[...]/_inc/" -I"[...]/_inc/" -I"[...]/_inc/" -I"[...]/_inc/" -I"[...]/_inc/" -I"[...]/_inc/" -I"[...]/_inc/" -I"[...]/_inc/" -I"[...]/_inc" -I"[...]/include/" -I"[...]/_inc/" -I"[...]/_inc/" -I"[...]/_inc/[...]/" -I"[...]/inc/" -I"[...]/_inc/" -I"[...]/_inc" -I"[...]/_inc" -I"[...]/_inc" -I"[...]/_inc" -I"[...]/_inc" -I"[...]/_inc" -I"[...]/_inc" -I"[...]/_inc" -I"[...]/_inc" -I"[...]/_inc" -I"[...]/_inc" -I"[...]/_inc" -I"[...]/_inc" -I"[...]/_inc" -g -gdwarf-3 -gstrict-dwarf -Wall -std=c99 -Wno-sizeof-pointer-memaccess -xc -g -MMD -MP -MF"_src/[...].d" -MT"_src/[...].d"   -o"_src/[...].o" "[...]/_src/[...].c"

Additional setting in "CompilerOptions_ARM_Debug.txt":

-mcpu=cortex-a15
-mtune=cortex-a15
-mfloat-abi=hard 
-mfpu=neon-vfpv4 
-ffast-math 
-fno-unsafe-math-optimizations
-ftree-vectorize 

-Wno-comment 
-Wno-switch 
-Wno-unknown-pragmas
-Wno-misleading-indentation
-Wno-stringop-truncation

-Wcpp 
-Wsign-compare 
-Wtype-limits 
-Wenum-compare 
-Wstrict-aliasing

-Werror=sign-compare
-Werror=enum-compare
-Werror=type-limits
-Werror=pointer-sign
-Werror=strict-aliasing
-D__USE_GNU
-D_GNU_SOURCE
-fPIC
-pthread
-ggdb
-D_DEBUG

    3) We always use the compiler from the SDK, I checked that with all code composer versions

  • 0 in reply to Ruediger Casper
    TI__Guru 50045 points

    You can try add "-Wno-error" option so warning is not treated as error.

    Or, you can remove all "-Werror" options.

  • 0 in reply to Stanley Liu
    Prodigy 205 points

    This is not a general problem but a problem with my specific PC, as my colleagues that are compiling with the exact same settings do not have this problem. Altering the compiler settings cannot be the solution, as #warning is not treated as an error by gcc, but by Code Composer!

  • 0 in reply to Ruediger Casper
    TI__Guru 50045 points

    Did you try to start from a fresh installation?

    As you mentioned, this is specific on your PC so it is difficult to comment what the issue is.

    On a separate note, for SDK build, we typically just compile the code from command window without the use of CCS.

    Is there any reason you have to compile the code in CCS?

  • 0
    Prodigy 205 points

    Solved it myself today: The issue is with the language setting of gcc. The compiler issued messages in german, and CCS was unable to parse that. I changed my language to english and the problem was gone.