Changes between Version 5 and Version 6 of LoritoRoadmap

Show
Ignore:
Timestamp:
05/25/10 22:05:33 (12 years ago)
Author:
allison
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • LoritoRoadmap

    v5 v6  
    2222 * Figure out how to make user-defined ops (i.e. ops defined in Lorito) work. 
    2323 * Define PIR -> Lorito translation. 
    24  * Define Lorito -> C code translation. 
     24 * Define Lorito -> C code translation (this is a JIT, among other things) 
    2525 * Define Lorito -> C function translation (similar to the current function-based runcore). 
    2626 
    2727=== opsc (full HLLs) === 
    28  * Make opsc able to process HLLs and spit out Lorito ops.  Implement some ops in terms of a HLL. 
     28 * Make opsc able to process HLLs and spit out Lorito ops.  Implement some ops in terms of a HLL. [ANR: by "HLLs" you don't mean Perl/Python, but the mini-language that compiles down to Lorito ops?] 
    2929 
    3030=== Lorito PMCs === 
    … …  
    3636 * Modify the current PIR compiler to emit Lorito. 
    3737 * Implement core PIR ops in Lorito.   
    38  * Change the PBC to be Lorito-based instead of PIR-based. 
     38 * Change the PBC to be Lorito-based instead of PIR-based. [ANR: this will hugely bloat our bytecode, a higher-level of abstraction has advantages here] 
    3939 * Make the final switch. All ops and PMCs get compiled into L1 during the normal build process (possibly using a bootstrapping step). 
    4040