Changes between Version 44 and Version 45 of DataParallel/VectPragma


Ignore:
Timestamp:
Aug 20, 2012 2:49:14 AM (20 months ago)
Author:
chak
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DataParallel/VectPragma

    v44 v45  
    4747indicates that the type `T` should be automatically vectorised even if it is imported.  This is the default for all data types declared in the current module. If the type embeds no parallel arrays, no special vectorised representation will be generated.  
    4848 
    49 The type constructor `T` must be in scope, but it may be imported.  'PData' and 'PRepr' instances are automatically generated by the vectoriser. 
     49The type constructor `T` must be in scope, but it may be imported.  `PData` and `PRepr` instances are automatically generated by the vectoriser. 
    5050 
    5151Examples are the vectorisation of types, such as `Maybe` and `[]`, defined in the `Prelude`. 
     
    5959directs the vectoriser to replace `T` by `T'` in vectorised code. Vectorisation of `T` is abstract in that constructors of `T` may not occur in vectorised code.  
    6060 
    61 The type constructor `T` must be in scope, but it may be imported.  'PData' and 'PRepr' instances must be explicitly defined — they are not automatically generated. 
     61The type constructor `T` must be in scope, but it may be imported.  `PData` and `PRepr` instances must be explicitly defined — they are not automatically generated. 
    6262 
    6363An example is the vectorisation of parallel arrays, where `[::]` is replaced by `PArray` during vectorisation, but the vectoriser never looks at the representation of `[::]`.