Changes between Version 5 and Version 6 of CompilationPhases


Ignore:
Timestamp:
12/30/08 21:52:19 (5 years ago)
Author:
ehuelsmann
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • CompilationPhases

    v5 v6  
    3232 3. Creating java 'instructions' from the small pieces 
    3333 
    34 The generated instructions differ from byte code in so far that they are not stored in arrays of octets, but instead in an array (or list) of 'instruction'-structures. 
     34The generated instructions differ from byte code in so far that they are not stored in arrays of octets, but instead in an array (or list) of 'instruction'-structures. The instructions generated by this phase are somewhat random and unoptimized. 
    3535 
    3636== Byte code munging phase == 
    3737 
    38 This phase does byte code calculations 
     38This phase does byte code calculations. One of the things this phase does, is generate the applicable byte codes - although it takes a half-harted stab at choosing the optimal ones, currently. 
    3939 
    4040 1. Analyzing the byte code, deleting unused branches (jvm.lisp::OPTIMIZE-CODE) 
     
    4545 4. Writing out a file according to the format specified for .class files 
    4646 
     47 
     48=== Resolvers === 
     49 
     50The third step in byte code munging is resolving byte codes to applicable byte codes. In this phase, similar byte codes - like bipush and sipush - are treated as the same. The actual applicable byte code is generated. 
     51 
     52The stab at generating good byte code is half-harted, because byte codes like iconst_1, aload_0, etc, are not used for optimal output.