Changes between Version 25 and Version 26 of GSoc2011

Show
Ignore:
Timestamp:
03/12/11 16:49:19 (11 years ago)
Author:
cotto
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GSoc2011

    v25 v26  
    5656 * '''Difficulty''': 4/5 
    5757 * '''Links of Interest''': <NONE, please add some> 
    58  * '''Possible Mentors''': <UNKNOWN, please volunteer!> 
     58 * '''Possible Mentors''': cotto 
    5959 * '''Details''': Several languages compile down to an abstract syntax tree type called POST. POST is the last stage of analysis and transformation before output code generation. Update existing POST, or create a new POST library capable of outputting bytecode directly. You should not output PIR and rely on the PIR compiler to generate the bytecode. Emphasis for this project is placed on the ability to output working bytecode, not necessarily on the quality of the generated bytecode nor the throughput performance of the converters. 
    6060 * '''Expected Deliverables''': A POST extension or POST replacement which is able to generate bytecode. Includes necessary unit tests and all necessary documentation. 
     
    9696 * '''Difficulty''': 4/5 
    9797 * '''Links of Interest''': <NONE, please add some> 
    98  * '''Possible Mentors''': Whiteknight 
     98 * '''Possible Mentors''': Whiteknight, cotto 
    9999 * '''Details''': Parrot needs a new debugger. There exists a toolset called "parrot-instrument" which can be used to insert introspection, analysis, and manipulation functions into Parrot internals. You may optionally (preferrably) use Parrot-Instrument as the basis for your new debugger or create a new one from scratch. A successful debugger will have the ability to set break-points on subroutines at the PIR and HLL level, set watchpoints on registers or individual PMCs, and introspect state information from a running program. The debugger should read information from annotations so that it can be used to work with various HLLs. Performance of code executing under the debugger is not a primary concern for the initial deliverable. 
    100100 * '''Expected Deliverables''': A working debugger with the capabilities listed above. In addition, the successfull student should provide adequate unit tests, code examples, and documentation. 
     
    104104 * '''Difficulty''': 3/5 
    105105 * '''Links of Interest''': <NONE, please add some> 
    106  * '''Possible Mentors''': <UNKNOWN, please volunteer!> 
     106 * '''Possible Mentors''': cotto 
    107107 * '''Details''': Several HLLs, especially Rakudo Perl 6, have need of a profiling tool that can generate information about subroutine call patterns and execution times. This will help to identify bottlenecks and areas where optimization is needed, among other things. There exists a project called "Parrot-Instrument" which can be used to add analysis, introspection, and runtime manipulation tools to Parrot. Parrot-Instrument may be used as the basis for a successful code profiling tool. Ideally, the code profiling tool will operate on PIR/PBC and will be agnostic to the specific HLL in which the code was originally written. 
    108108 * '''Expected Deliverables''': A working code profiling tool including unit testing and user documentation.