deep

a Cross Development Platform for Java

User Tools

Site Tools


dev:start

Differences

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

Link to this comparison view

Next revision
Previous revision
dev:start [2014/06/10 07:16] – external edit 127.0.0.1dev:start [2022/12/20 11:30] (current) ursgraf
Line 1: Line 1:
 +<WRAP group>
 +<WRAP half column 58%>
 ====== Project deep ====== ====== Project deep ======
-<box 40right green | Installation for Developers>+Under the name of **deep** a cross development platform for Java was created. The project was initiated and is maintained by the Institut for Computer Science at the Eastern Switzerland University of Applied Sciences, OST, Buchs, Switzerland.  
 + 
 +===== Goals ===== 
 +  * Development platform for Java including compiler, linker and runtime system. 
 +  * Focus on efficiency, for the core of the compiler very lightweight data structures are used, the powerful but slow Java library is solely used for odd tasks. 
 +  * Supports newest Java version. 
 +  * Integration into eclipse, but can be run stand-alone as well. 
 +  * "Java on the metal": Java programs are translated with regular JDK into Bytecode, **deep** translates this Bytecode directly into machine code. 
 +  * No object files, a launch translates all necessary classes into target image 
 +  * Runtime library is simplified standard library. 
 +  * A fast and lightweight path to the underlying hardware with registers and absolute memory locations is provided. 
 +</WRAP> 
 + 
 +<WRAP half column 38%> 
 +<box 80% green right | Installation for Developers>
   * [[.:installation_for_developers|Installation for Developers]]   * [[.:installation_for_developers|Installation for Developers]]
 </box> </box>
-Under the name of **deep** a new cross development platform for Java was created. The project was initiated and is maintained by the Institut for Computer Science at the Fachhochschule für Technik, NTB, Buchs, Switzerland.  +<box 80 red right | Components>
-<box 40right red | Components>+
   * [[.:launcher|Launcher]]   * [[.:launcher|Launcher]]
   * [[.:configuration|Configuration]]   * [[.:configuration|Configuration]]
Line 14: Line 29:
   * [[.:file_formats]|File Formats]]   * [[.:file_formats]|File Formats]]
   * [[.:HString|HStrings (String-Handling in the Compiler)]]   * [[.:HString|HStrings (String-Handling in the Compiler)]]
 +  * [[openocd:start|OpenOCD]]
 +  * [[.:Zynq7000PL]|PL Configuration on the Zynq7000]]
 </box> </box>
-===== Goals ===== +</WRAP> 
-  * Development platform for Java including compiler, linker and runtime system. +</WRAP> 
-  * Focus on efficiency, for the core of the compiler very lightweight data structures are used, the powerful but slow Java library is solely used for odd tasks. +
-  * Supports newest Java version. +
-  * Integration into eclipse, but can be run stand-alone as well. +
-  * "Java on the metal": Java programs are translated with regular JDK into Bytecode, **deep** translates this Bytecode directly into machine code. +
-  * No object files, a launch translates all necessary classes into target image +
-  * Runtime library is simplified standard library. +
-  * A fast and lightweight path to the underlying hardware with registers and absolute memory locations is provided.+
  
 ===== Overview ===== ===== Overview =====
Line 29: Line 40:
  
 ===== 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 [[.:CrossCompiler:SSA|Static Single Assignment Form, SSA]]. This form is simple and platform independent and can be used for various optimizations. In a second step, which is platform specific, registers are allocated and code is generated. +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 [[.:CrossCompiler:SSA|Static Single Assignment Form, SSA]]. This form is simple and platform independent and can be used for various optimizations. In a second step, which is platform specific, registers are allocated and code is generated. 
  
 ==== Frontend ==== ==== Frontend ====
Line 36: Line 47:
 ==== 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 and ARMv7 code can be generated. As target processors we use mpc555 and mpc5200 for PowerPC and the Zynq-7000 with a dual core ARM Cortex-A9 processor as an ARM target
  
 ===== Further Components ===== ===== Further Components =====
Line 42: Line 53:
  
 ==== Class File Browser ==== ==== Class File Browser ====
-When working extensively with class files our **Class File Browser** might be advantageous. It displays all information of a class file in easily readable form. It can downloaded as an eclipse plugin from [[https://marketplace.eclipse.org/content/eclipse-class-file-browser]].+When working extensively with class files our **Class File Browser** might be advantageous. It displays all information of a class file in easily readable form. It can be downloaded as an eclipse plugin from [[https://marketplace.eclipse.org/content/eclipse-class-file-browser]].
  
 ==== Runtime System ==== ==== Runtime System ====
Line 56: Line 67:
 Many views in eclipse support the viewing of variables, objects, registers and memory sections. We also deploy the debugger framework of eclipse to support target debugging with setting breakpoints and single-stepping (see [[.:eclipse_debugger|Debugger]]). Many views in eclipse support the viewing of variables, objects, registers and memory sections. We also deploy the debugger framework of eclipse to support target debugging with setting breakpoints and single-stepping (see [[.:eclipse_debugger|Debugger]]).
  
 +----
 +==== Internal Developer Documentation ====
 +The internal documentation for maintainers can be found  [[http://wiki.bu.ost.ch/collaboration/deep/start|here]].
  
dev/start.1402377389.txt.gz · Last modified: 2016/02/25 13:33 (external edit)