MSPM0-SDK: compilation error with no indication

I removed all confidential parts from the compilation chain.

What I noticed is that there's the following option, which we haven't enabled: -Wno-error=implicit-function-declaration
Is this normal?

[848] "C:\\ti\\ccs2031\\ccs\\tools\\compiler\\ti-cgt-armllvm_4.0.4.LTS\\bin\\tiarmclang.exe" -cc1 -triple thumbv6m-ti-none-eabi -emit-obj -disable-free -clear-ast-before-backend -disable-llvm-verifier -discard-value-names -main-file-name pspUart.c -mrelocation-model static -mframe-pointer=none -fmath-errno -ffp-contract=on -fno-rounding-math -mconstructor-aliases -nostdsysteminc -fno-zero-initialized-in-bss -fdef-uninit-in-bss -fcommon -ffunction-sections -fdata-sections -fno-delete-null-pointer-checks -fwchar-type=int -fshort-enums -mthread-model single -Wno-error=implicit-function-declaration -mllvm -enable-printf-attrs -mllvm -experimental-debuginfo-iterators=false -mllvm -loop-flatten-prefer-compares -target-cpu cortex-m0plus -target-feature +soft-float -target-feature +soft-float-abi -target-feature -crc -target-feature -dsp -target-feature -ras -target-feature -sb -target-feature -i8mm -target-feature -lob -target-feature -cdecp0 -target-feature -cdecp1 -target-feature -cdecp2 -target-feature -cdecp3 -target-feature -cdecp4 -target-feature -cdecp5 -target-feature -cdecp6 -target-feature -cdecp7 -target-feature -pacbti -target-feature -hwdiv-arm -target-feature -hwdiv -target-feature -vfp2 -target-feature -vfp2sp -target-feature -vfp3 -target-feature -vfp3d16 -target-feature -vfp3d16sp -target-feature -vfp3sp -target-feature -fp16 -target-feature -vfp4 -target-feature -vfp4d16 -target-feature -vfp4d16sp -target-feature -vfp4sp -target-feature -fp-armv8 -target-feature -fp-armv8d16 -target-feature -fp-armv8d16sp -target-feature -fp-armv8sp -target-feature -fullfp16 -target-feature -fp64 -target-feature -d32 -target-feature -neon -target-feature -dotprod -target-feature -fp16fml -target-feature -bf16 -target-feature -mve -target-feature -mve.fp -target-feature -fpregs -target-feature -crypto -target-feature -sha2 -target-feature -aes -target-feature +strict-align -target-abi aapcs -fvisibility=hidden -msoft-float -mfloat-abi soft -Wunaligned-access -debug-info-kind=constructor -dwarf-version=3 -debugger-tuning=gdb "-fdebug-compilation-dir= [remove part]

We tried with CCS version 20.02.00 and TiClang 4.0.3, and the errors are clearly visible in the problems tab.

After various tests, it appears that errors are not displayed if there are too many of them.

Hi,

Make sure you have defined and declared your functions correctly. 

You haven't given me much to work with, but I would eliminate files until you have a working build, and then start to add them again. Fix errors as you go.

-Matthew

We managed to correct our errors.

We reverted to CCS20.2, which correctly displays all compilation errors, unlike CC20.3.

Here is an example of an error that is correctly reported in CCS 20.2 Ti Clang 4.0.3 but was not present in CCS 20.3 Ti Clang 4.0.4.

In this scenario, we deleted the configuration element, but it wasn't removed from a structure.
Therefore, an error is expected, but it's not displayed in CC20.3.

Hi,

Glad to hear that it is resolved. 

-Matthew

You're not opening an issue for the next TICLANG revision?

Hi,

Could you provide the project details, so I can reproduce the issue?

-Matthew

ga jo said:

Here is an example of an error that is correctly reported in CCS 20.2 Ti Clang 4.0.3 but was not present in CCS 20.3 Ti Clang 4.0.4.

In this scenario, we deleted the configuration element, but it wasn't removed from a structure.
Therefore, an error is expected, but it's not displayed in CC20.3.

I already explained this in this message. You create a structure, for example:
typdef struct 
{

    uint32_t element_1;

}sStructTest;

You are instantiating it with an element that does not exist:

sStructTest structError = {.element_1=0, .element_2=0};

At this point you encounter a compilation error, but no information on the type of error.