• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 53 subscribers
  • Views 1866 views
  • Users 0 members are here
Support feedback
Options
Options

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.

Compiler: MISRA check generates a fatal error

Sasha Slijepcevic
Mastermind 37985 points
Other Parts Discussed in Thread: SYSBIOS

Tool/software: TI C/C++ Compiler

Here is my command line with relevant parts in red:

"C:/CCS7.3.0/ccsv7/tools/compiler/ti-cgt-arm_17.9.0.STS/bin/armcl" -mv7M4 --code_state=16 --float_support=FPv4SPD16 -me --include_path="C:/CCS7.3.0/ccsv7/ccs_base/arm/include" --include_path="C:/CCS7.3.0/ccsv7/ccs_base/arm/include/CMSIS" --include_path="C:/Users/a0868339/workspace_v7_3/alignmentTest" --include_path="C:/CCS7.3.0/ccsv7/tools/compiler/ti-cgt-arm_17.9.0.STS/include" --advice:power=all --define=__MSP432P401R__ --define=ccs --define=xdc_target_types="ti/sysbios/BIOS.h" -g --gcc --diag_warning=225 --diag_wrap=off --display_error_number --abi=eabi --check_misra="all" --preproc_with_compile --preproc_dependency="system_msp432p401r.d_raw" "../main.c"

Without --check_misra option, the compilation succeeds, but with --check_misra, it fails with the following error:
Command-line error #1046: invalid macro definition: xdc_target_types=ti/sysbios/BIOS.h
1 catastrophic error detected in the compilation of "../main.c".

Is that supposed to happen? Should MISRA checks only tag the problems and let the compilation finish as if there were no checks? How should I set a macro on the command line without triggering this error?

I haven't seen this problem with the 16.9.4 compiler. There is nothing special about main.c, it's basically a blink LED type of a test.

  • 0
    TI__Guru**** 244280 points

    I'm not sure what is going on.  I can reproduce it.  I filed CODEGEN-4346 in the SDOWP system to have this investigated.  You are welcome to track it with the SDOWP link below in my signature.

    Thanks and regards,

    -George

  • 0
    TI__Guru* 84225 points
    That command line violates MISRA-C rule 19.4: "C macros shall only expand to a braced initialiser, a constant, a string literal, a parenthesised expression, a type qualifier, a storage class specifier, or a do-while-zero construct." You are setting the macro xdc_target_types to the sequence of characters [ti/sysbios/BIOS.h] without the square brackets. If you want the quotation marks to be part of the macro definition, you will need to quote them to prevent the shell from interpreting them:

    --define=xdc_target_types=\"ti/sysbios/BIOS.h\"

    It is a bit weird that this diagnostic does not explicitly say it is due to MISRA; I'll change CODEGEN-4346 to be report against that issue.
  • 0 in reply to Archaeologist
    TI__Mastermind 37985 points
    I understand that I am breaking a MISRA rule, but I was surprised that the compilation stopped there. I guess that means that --misra_required is set to 'error' by default.