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.

  • Resolved

Interrupt declaration msp430-elf: internal compiler error

Prodigy 50 points

Replies: 1

Views: 1124

Declaring an interrupt the 4.7.0 way results in an internal compiler error on 4.9.1:

__attribute__((__interrupt__ (NMI_VECTOR)))
static void  NMI_int(void)
{

}

Only if I replace __interrupt__ with 'interrupt' compilation goes fine.

OTOH if I replace __interrupt__ with some bogus value like 'paashaas' I get the following error: main.c:164:1: warning: ‘paashaas’ attribute directive ignored [-Wattributes]

Internal compiler error below:

/opt/msp430-elf/bin/msp430-elf-gcc -c -DINCLUDE_RNG_CODE -DMSP430_UNIARCH -Dmsp430f1232 -DMSP_CODE -Os -g -Wall --std=gnu99 -mcpu=430 -mmcu=msp430f1232 -Wa,-adhlns=main.lst,-mcpu=430  main.c -o main.o
main.c:164:1: internal compiler error: in msp430_attr, at config/msp430/msp430.c:1208
 {
 ^
0x9aa23d msp430_attr
    ../../tools/gcc/config/msp430/msp430.c:1208
0x4a7798 decl_attributes(tree_node**, tree_node*, int)
    ../../tools/gcc/attribs.c:565
0x4b4551 start_function(c_declspecs*, c_declarator*, tree_node*)
    ../../tools/gcc/c/c-decl.c:7868
0x4eb2ef c_parser_declaration_or_fndef
    ../../tools/gcc/c/c-parser.c:1892
0x4eef65 c_parser_external_declaration
    ../../tools/gcc/c/c-parser.c:1415
0x4efa09 c_parser_translation_unit
    ../../tools/gcc/c/c-parser.c:1302
0x4efa09 c_parse_file()
    ../../tools/gcc/c/c-parser.c:14074
0x52d0f4 c_common_parse_file()
    ../../tools/gcc/c-family/c-opts.c:1067
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <http://gcc.gnu.org/bugs.html> for instructions.
make: *** [main.o] Error 1


  • Thank you for notifying us of this problem. I can reproduce it. An issue has been filed with the developers. You can track SDSCM00051276 with the SDOWP link below in my signature.

    Thanks and regards,

    -George

    TI C/C++ Compiler Forum Moderator
    Please click This Resolved My Issue on the best reply to your question
    The CCS Youtube Channel
     has short how-to videos
    The 
    Compiler Wiki answers most common questions
    Track an issue with SDOWP. Enter your bug id in the Search box.

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.