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

weird issue in arm code called by C function

Parents
  • Note: This was originally posted on 21st March 2013 at http://forums.arm.com

    You time measurement is also likely to be wildly inaccurate. You are needing a system call either side of the memmove or the ARM function to get the time. The system call is going to take a lot longer than code it is timing (which is likely to be much shorter than the time granularity, depending on the clock speed you have).

    Loop the memmove and the ARM function so they take a second or so to run, and time that.
Reply
  • Note: This was originally posted on 21st March 2013 at http://forums.arm.com

    You time measurement is also likely to be wildly inaccurate. You are needing a system call either side of the memmove or the ARM function to get the time. The system call is going to take a lot longer than code it is timing (which is likely to be much shorter than the time granularity, depending on the clock speed you have).

    Loop the memmove and the ARM function so they take a second or so to run, and time that.
Children
No data