Changes between Version 20 and Version 21 of Commentary/Compiler/IntegratedCodeGen


Ignore:
Timestamp:
Jun 9, 2008 11:29:52 AM (6 years ago)
Author:
simonpj
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Commentary/Compiler/IntegratedCodeGen

    v20 v21  
    123123Interfaces like these would require the machine-specific abstract type `i` to contain enough information to reconstruct a `LocalReg` or `CmmExpr`.  Later one, we'll need to construct SRTs too, so we must continue to track pointer-hood. 
    124124 
    125 One possible implementation for `I386` or `Sparc` would be to use a generic RTL representation, together with a recogniser to maintain the machine invariant.  Our initial idea, though, is that  is an implementation choice.   
     125One possible implementation for `I386` or `Sparc` would be to use a generic RTL representation, together with a recogniser to maintain the machine invariant.  Our initial idea, though, is that  is an implementation choice.  It's still possible that a machine-independent optimisation could take advantage of the representation being an RTL. For example, we could provide a function in the `Instr` class 
     126{{{ 
     127   rtl :: i -> RTL 
     128}}} 
     129which is particularly cheap for architectures that do use `RTL` as the representation type. 
    126130 
    127131=== Optimisation ===