deep

a Cross Development Platform for Java

User Tools

Site Tools


dev:crosscompiler:backend_ppc:exceptions

Differences

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

Link to this comparison view

Next revision
Previous revision
dev:crosscompiler:backend_ppc:exceptions [2016/02/25 13:33] – external edit 127.0.0.1dev:crosscompiler:backend_ppc:exceptions [2019/08/27 12:30] (current) ursgraf
Line 21: Line 21:
 ===== Java Exceptions ===== ===== Java Exceptions =====
 ==== Program Exception ==== ==== Program Exception ====
-Each Java exception causes a PPC program exception. The handler receives the thrown exception like a parameter in the first parameter register R2. The code generator has to make sure that this parameter is copied into R2 during the prolog of the program exception handler. The handler does the following:+Each Java exception causes a PPC program exception. The handler receives the thrown exception as a parameter in the first parameter register R2. The code generator has to make sure that this parameter is copied into R2 during the prolog of the program exception handler. The handler does the following:
   * Get address of causing instruction into variable //addr// from SRR0.   * Get address of causing instruction into variable //addr// from SRR0.
   * Read instruction at this address   * Read instruction at this address
Line 43: Line 43:
  
 The figure below gives an example for the handling of exceptions. The figure below gives an example for the handling of exceptions.
-[{{ .:exceptionoverview.png?700 | //Example for handling of exceptions//}}] +[{{ .:exceptionoverviewppc.png?700 | //Example for handling of exceptions//}}] 
dev/crosscompiler/backend_ppc/exceptions.txt · Last modified: 2019/08/27 12:30 by ursgraf