• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 52 subscribers
  • Views 437 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Save On Call / Save On Entry Properties of DP

randy.yates
Prodigy 355 points

In SPRU514D it is shown in Table 7-2 that the DP   is neither "Save on Entry" nor "Save on Call." How can this be? If a register is not SOE, then the caller must save it, i.e., it must be SOC. 

In other words, the SOE/SOC columns should be logical inverses of one another, and DP is not. So how is this possible?

--Randy

 

  • 0
    TI__Guru**** 253380 points

    This is an error in the documentation.  The DP is save on call.  I filed SDSCM00042503 in the SDOWP system to have the book updated.  Feel free to track it with the SDOWP link below in my sig.

    FWIW ... The compiler never preserves the DP across a function call.  Instead, the compiler always presumes a function call trashes the contents of DP.  The same is true of all the save on call registers.

    Thanks and regards,

    -George