Mercurial > hg > truffle
comparison graal/GraalCompiler/src/com/sun/c1x/doc/backend_open_issues.txt @ 2509:16b9a8b5ad39
Renamings Runtime=>GraalRuntime and Compiler=>GraalCompiler
| author | Thomas Wuerthinger <thomas@wuerthinger.net> |
|---|---|
| date | Wed, 27 Apr 2011 11:50:44 +0200 |
| parents | graal/Compiler/src/com/sun/c1x/doc/backend_open_issues.txt@9ec15d6914ca |
| children |
comparison
equal
deleted
inserted
replaced
| 2508:fea94949e0a2 | 2509:16b9a8b5ad39 |
|---|---|
| 1 Remaining Issues in the C1X backend (after the port July-Sep 09) | |
| 2 ====================================================================== | |
| 3 | |
| 4 Maxine/Inspector Related Open Issues: | |
| 5 - Global stubs: Change calling convention (no longer write to callee stack as this makes stepping through the instructions for saving the parameters to global stubs impossible in the inspector) | |
| 6 - Reference maps: Corrently implement TargetMethod.prepareReferenceMap for C1XTargetMethod (checking for the need to stack walk a possible callee saved target method) and call it from Maxine | |
| 7 - Disassembler: The Maxine disassembler still does not correctly display every machine code instruction issued by C1X | |
| 8 - MaxRiRuntime and C1XTargetMethod have fixed dependencies on the X86 parts (instruction decoding, registers, calling convention), should be factored out | |
| 9 | |
| 10 Compile-Time Performance Improvements: | |
| 11 - Consider deleting the LIRItem class | |
| 12 - Make sure that LIROperand objects are not shared among LIR instructions and can therefore be directly modified by the LinearScan register allocator (no more need for the lazy creation of LIRAddress objects in the LIRInstruction class) | |
| 13 | |
| 14 Run-Time Performance Improvements: | |
| 15 - Store mapping between machine code location and bytecode index in the target method (remove arguments from global stub calls), this decreases the number of necessary parameters especially for resolution instructions. | |
| 16 - Use Inline Cache on virtual method calls | |
| 17 | |
| 18 Better Portability: | |
| 19 - Integrate XIR; consider using CiLocation / CiConstant in XIR | |
| 20 - The JIT adapter frames should be a more general mechanism that receives two calling conventions (in form of an array of locations) and adapts between them automatically | |
| 21 - Have the possibility to register intrinsics by specifying XIR code | |
| 22 |