• State Accepted Answer
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 351 subscribers
  • Views 1027 views
  • Users 0 members are here
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

Cortex-R52+ floating-point register pop and push

Grace WANG

Hi 

We found the issue when using floating-point calculations in the mulitple ISR, then the floating-point number will be not as expected sometimes.

After adding "VPUSH {D0-D15}" in the beginning of the interrupt callback and adding "VPOP {D0-D15}" in the end of the interrupt callback, the issue will not occur anymore.

I think the cause is the floating-point register set is not automatically saved and restored for Cortex-R52+, is that right ?

What is the suggestion for such issue ?

Is it necessary to pop and push FPSCR manually ?

BR, Grace

Parents
  • +1 Arm Employee Badge in reply to Grace WANG

    Yeah, I suspect that's because of the assumption that a lot of interrupt handler code will avoid the FP registers to save the overhead.

    In terms of a list, it's more the other way around.  The architecture lists those registers which are updated on exception entry/exit.  Any other register you update, or cause to be updated, that effects where the exception was taken from potentially has to be saved/restored.  The architecture doesn't spell it out as you might deliberately choose to save/restore some registers.  For example, you might use registers to pass arguments in and out of a system call.

Reply
  • +1 Arm Employee Badge in reply to Grace WANG

    Yeah, I suspect that's because of the assumption that a lot of interrupt handler code will avoid the FP registers to save the overhead.

    In terms of a list, it's more the other way around.  The architecture lists those registers which are updated on exception entry/exit.  Any other register you update, or cause to be updated, that effects where the exception was taken from potentially has to be saved/restored.  The architecture doesn't spell it out as you might deliberately choose to save/restore some registers.  For example, you might use registers to pass arguments in and out of a system call.

Children
No data