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/16 14:14] – [Stackframe] ursgraf | dev:crosscompiler:backend_arm:code_generator [2019/07/19 16:58] – [Code Generator for ARM] ursgraf | ||
---|---|---|---|
Line 3: | Line 3: | ||
^topic^I^L^F^remarks^ | ^topic^I^L^F^remarks^ | ||
|throw| ||| | | |throw| ||| | | ||
- | |new| |||primitive array & array of objects & string implemented| | + | |new| |||tests for three dimensional arrays fail| |
+ | |enum| |||tests for enums fail| | ||
|exceptions| ||| | | |exceptions| ||| | | ||
Line 16: | Line 17: | ||
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 calling interface methods some temporary space on the stack might be necessary. | + | 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 some temporary space on the stack might be necessary |
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. |