This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
dev:crosscompiler:backend_arm:code_generator [2019/07/11 19:40] – [Compiler Specific Subroutines] ursgraf | dev:crosscompiler:backend_arm:code_generator [2019/07/11 19:46] – [Code Generator for ARM] ursgraf | ||
---|---|---|---|
Line 5: | Line 5: | ||
|checkcast| ||| | | |checkcast| ||| | | ||
|throw| ||| | | |throw| ||| | | ||
- | |call| |||class & instance methods can be called| | ||
|new| |||primitive array & array of objects & string implemented| | |new| |||primitive array & array of objects & string implemented| | ||
|exceptions| ||| | | |exceptions| ||| | | ||
Line 19: | Line 18: | ||
Important: volatile EXTR's must be saved as well if '' | Important: volatile EXTR's must be saved as well if '' | ||
- | The field //local variables// is only used if the number of registers does not suffice and locals must be assigned a slot on the stack. When dealing with FPR' | + | The field //local variables// is only used if the number of registers does not suffice and locals must be assigned a slot on the stack. When calling interface methods |
The field // | The field // | ||
The stack pointer always points to the top of the actual frame. At the top the stack pointer of the caller has to be stored. The back chain pointer is used for the debugger, for exceptions and for the garbage collection. | The stack pointer always points to the top of the actual frame. At the top the stack pointer of the caller has to be stored. The back chain pointer is used for the debugger, for exceptions and for the garbage collection. |