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.

  • TI Thinks Resolved

Compiler/MSP430-GCC-OPENSOURCE: Warning: a NOP might be needed here because of successive changes in interrupt state

Prodigy 140 points

Replies: 1

Views: 457

Part Number: MSP430-GCC-OPENSOURCE

Tool/software: TI C/C++ Compiler

This issue was reported more than a year ago (https://e2e.ti.com/support/development_tools/compiler/f/343/t/502857) and TI offered to notify the developer about it.

However it is still present even in the latest MSP430-GCC release (5.1.1.0) - I also tried several previous releases and they all have it.

The Warnings are very annoying and confusing inside a development team environment. I use the simpliciti stack which enables/disables interrupts in lots of places hence generates a huge amount of these warnings.

Also note that the switch -mY which is supposed to take care of it is not accepted by MSP430-elf-gcc.exe. The switch causes the compiler to stop so can't be used..

Please have Somnium take a look and resolve it asap.

  • I apologize for the trouble.

    Since that bug was first reported, we started filing and tracking bugs on MSP430 GCC tools in the SDOWP system.  For this issue, I filed MSPGCC-5.  You are welcome to follow it with the SDOWP link below in my signature.

    As can be seen on the release announcement for version 5.1.1.0 ...

    Somnium is no longer providing mspgcc releases for TI. This will be the final mspgcc release for the 6.x branch. TI is investigating options.

    For this reason, I am unable to say when this bug will be addressed.

    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.