Files
Xenia-Canary/src/alloy
2014-08-21 22:46:12 -07:00
..
2014-08-21 20:49:47 -07:00
2014-08-21 22:27:33 -07:00
2014-08-21 20:49:47 -07:00
2014-08-21 20:49:47 -07:00
2014-07-10 20:20:00 -07:00
2014-08-21 20:49:47 -07:00
2014-08-20 22:22:47 -07:00
2014-08-21 22:27:33 -07:00
2014-08-21 20:49:47 -07:00
2014-08-21 20:49:47 -07:00
2014-08-20 11:35:22 -07:00
2014-08-21 20:49:47 -07:00
2014-08-21 20:49:47 -07:00
2014-08-21 20:49:47 -07:00
2014-08-21 20:49:47 -07:00
2014-08-21 20:49:47 -07:00
2014-08-21 20:49:47 -07:00

alloy: small dynamic recompiler engine

Alloy is a transpiler framework that allows for pluggable frontends for decoding guest machine instructions (such as PPC) and pluggable backends for generating host code (such as x64). It features an SSA IR designed to model machine instructions and vector operations and compilation passes that seek to efficiently optimize previously-optimized code.

Future versions will cache generated code across runs and enable offline precompilation.

Frontends

Frontends are responsible for translating guest machine instructions into IR. Information about the guest machine and ABI is used to support efficient CPU state accesses and debug information.

  • PPC64 with Altivec extenions

Backends

A backend takes optimized IR and assembles an implementation-specific result. The backend is also responsible for executing the code it generates and supporting debugging features (such as breakpoints).

  • IVM: bytecode interpreter
  • x64: IA-64 with AVX2 code generator