This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
dev:start [2017/03/20 09:58] – sfink | dev:start [2019/02/25 16:40] – [Crosscompiler] ursgraf | ||
---|---|---|---|
Line 29: | Line 29: | ||
* [[.: | * [[.: | ||
* [[.: | * [[.: | ||
+ | * [[openocd: | ||
</ | </ | ||
</ | </ | ||
Line 38: | Line 39: | ||
===== Crosscompiler ===== | ===== Crosscompiler ===== | ||
- | Our **deep** compiler translates Bytecode into machine code for a certain processor. To optimize for speed and code size and to make use of register based architecture - such as PPC - we transform the Bytecode in a first step into [[.: | + | Our **deep** compiler translates Bytecode into machine code for a certain processor. To optimize for speed and code size and to make use of register based architecture - such as PPC or ARM - we transform the Bytecode in a first step into [[.: |
==== Frontend ==== | ==== Frontend ==== | ||
Line 45: | Line 46: | ||
==== Backend ==== | ==== Backend ==== | ||
For each supported architecture a specific backend is necessary. As a first step, registers are assigned for all SSA instruction results. After this machine instructions can be issued for the target. Finally the linker combines everything into a executable target image.\\ | For each supported architecture a specific backend is necessary. As a first step, registers are assigned for all SSA instruction results. After this machine instructions can be issued for the target. Finally the linker combines everything into a executable target image.\\ | ||
- | Currently, PowerPC code can be generated. As target processors we use mpc555 and mpc5200. | + | Currently, PowerPC |
===== Further Components ===== | ===== Further Components ===== |