Changes between Version 11 and Version 12 of DataParallel/WorkPlan


Ignore:
Timestamp:
Feb 10, 2009 8:58:22 AM (5 years ago)
Author:
chak
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DataParallel/WorkPlan

    v11 v12  
    55 
    66 0. '''DUE 6 March.''' Solve major performance and scalability problems for our current benchmarks.  Try to get a performance advantage over plain Haskell on !LimitingFactor (i.e., 8 cores). 
    7  0. '''DUE 30 March.''' Presentation for ''Microsoft External Research Symposium''. 
     7 0. '''DUE 30 March.''' Presentation/poster for ''Microsoft External Research Symposium''. 
    88 
    99=== Task assignments === 
    1010 
    1111 ''Roman'':: 
    12    '''New build system''', '''Template Haskell''', '''Replicate''', #2984 & '''Recycling''' 
     12   '''Template Haskell''', '''Replicate''', #2984 & '''Recycling''' 
    1313   – status: partly implemented, but still needs serious work 
    1414   * To use the special representation of task '''Replicate''' most effectively, we would ''again'' need different views on arrays together with a cost function and optimisation rules taking the cost function into account.  That requires a lot of work! 
    1515   * We decided that, for the moment, Roman will first try to integrate the replication representation directly and see how far that gets us.  Maybe it helps at least with some examples and gives us something somewhat usable more quickly. 
    16    * However, before any further major changes to the library, Roman needs to first re-arrange things such that the library boilerplate is generated, instead of being hardcode; otherwise, changes require a lot of tiresome code editing.  Unfortunately, that lands us in build system hell again, as we can only use TH if package dph is built in stage2.  (Is this easy(?) to achieve with the current build system, or do we want the new one for that?) 
     16   * However, before any further major changes to the library, Roman needs to first re-arrange things such that the library boilerplate is generated, instead of being hardcode; otherwise, changes require a lot of tiresome code editing.   
    1717 
    1818 ''Simon'':: 
     
    7070Category: ''Infrastructure'' (fiddling with GHC's build system and similar infrastructure): 
    7171 
    72  * '''New build system:''' Evaluate whether the preview of the new build system looks like it is what we want 
    73  
    7472 * '''Template Haskell:''' Arrange for package DPH to be build in stage2, so that we can use TH to generate library boilerplate & rewrite the library to generate the boilerplate that's currently hardcoded. 
    7573 
     
    7876=== Done === 
    7977 
     78 * '''New build system:''' Evaluate whether the preview of the new build system looks like it is what we want.  [The new build system seems fine and we should have no problem building package dph in stage2 either.] 
     79 
    8080 * '''!CoreToStg''': Compiling package dph with the HEAD currently results in `ASSERT failed! file stgSyn/CoreToStg.lhs line 239` (with a DEBUG compiler). 
    8181