deep

a Cross Development Platform for Java

User Tools

Site Tools


dev:crosscompiler:backend_ppc:register_allocation

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
dev:crosscompiler:backend_ppc:register_allocation [2018/12/11 17:24]
ursgraf [Register Usage]
dev:crosscompiler:backend_ppc:register_allocation [2018/12/20 17:14] (current)
ursgraf [Register Usage]
Line 3: Line 3:
  
 ===== Register Usage ===== ===== Register Usage =====
-Registers can be classified as //​dedicated//,​ //​volatile//​ or //​nonvolatile//​. //​Dedicated//​ are register with a special purpose, such as the stackpointer. //​Volatile//​ means, that this register might be used any time. It does not have to be stored when another method is called. //​Nonvolatile//​ registers must be saved in the prologue of a method before they can be used and after use they must be restored. The number of volatile and nonvolatile registers must be equal for all methods. ​+
 | Register | State | Use | | Register | State | Use |
 | R0 | volatile | method prologue, scratch register | | R0 | volatile | method prologue, scratch register |
dev/crosscompiler/backend_ppc/register_allocation.txt · Last modified: 2018/12/20 17:14 by ursgraf