• Locked Locked
  • Replies 9 replies
  • Subscribers 119 subscribers
  • Views 4838 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

CM3 / RVDS / NOPs

David Clark
Parents
  • Note: This was originally posted on 14th June 2010 at http://forums.arm.com

    Please check out the definition of the above macro(?). I am sure these NOPs get generated explicitly.

    Regards
    Marcus


    Hi Marcus,

    Thanks for your reply.  Actually, the macro just expands to  __disable_irq()

    I should have included that information initially.  There are other examples of what seem to be lots of NOPs, some that have nothing to do w/ interrupts, I'll put in another example below.

    Hi Joseph,

    Thanks for your reply.  I'll follow up w/ a post on my configuration, I suspect it's similar if not identical, but I'll get the toolset config & post back.

    It's interesting that the __disable_irq() intrinsic didn't generate the NOPs for you.  I suppose a cut & paste of my compiler command line would probably also be useful.

    I'll post back with a) the toolset config, B) the compiler command line, and c) another example that has lots of NOPs that doesn't manipulate interrupts at all.  I realize it's very difficult to troubleshoot / understand / explain a compiler's behavior without the full picture, it's just that right now I'm not at liberty to paste in full chunks of source code.  I'll try to create a standalone mini-test case, that would probably get us the most useful information right away.

    Thanks to you both, back soon.
Reply
  • Note: This was originally posted on 14th June 2010 at http://forums.arm.com

    Please check out the definition of the above macro(?). I am sure these NOPs get generated explicitly.

    Regards
    Marcus


    Hi Marcus,

    Thanks for your reply.  Actually, the macro just expands to  __disable_irq()

    I should have included that information initially.  There are other examples of what seem to be lots of NOPs, some that have nothing to do w/ interrupts, I'll put in another example below.

    Hi Joseph,

    Thanks for your reply.  I'll follow up w/ a post on my configuration, I suspect it's similar if not identical, but I'll get the toolset config & post back.

    It's interesting that the __disable_irq() intrinsic didn't generate the NOPs for you.  I suppose a cut & paste of my compiler command line would probably also be useful.

    I'll post back with a) the toolset config, B) the compiler command line, and c) another example that has lots of NOPs that doesn't manipulate interrupts at all.  I realize it's very difficult to troubleshoot / understand / explain a compiler's behavior without the full picture, it's just that right now I'm not at liberty to paste in full chunks of source code.  I'll try to create a standalone mini-test case, that would probably get us the most useful information right away.

    Thanks to you both, back soon.
Children
No data