Futhask
Futhask is a code generator that aims to create safe, Haskell friendly wrappers for Futhark libraries.
Installation
stack install
Use
Generate Code
futhask [Backend] [Futhark.h] [HaskellSourceDir] [ModuleName]
Example
futhark opencl --library myprogram.fut
futhask opencl myprogram.h src MyLibrary
For a simple example of how generated haskell code can be used, see FuthaskExample
Import Code
import [ModuleName]
import [ModuleName].Entries
If using stack
add c-sources: [Futhark.c]
to the library
section of package.yaml
OpenCL
extra-libraries: OpenCL
CUDA
include-dirs: /opt/cuda/include
extra-lib-dirs: /opt/cuda/lib
extra-libraries: cuda cudart nvrtc
Dependencies
transformers
and massiv
are required for all backends.
The codes generated for OpenCL and CUDA, both refer to types from the OpenCL
and cuda
packages respectively. This is only relevant if one wants to use certain functions in the raw interface, but, without modification, the generated code will not compile without these dependencies.
Generated Code
The generated code can be split in two main parts, raw and wrapped. The raw interface is simply the C-functions wrapped in the IO
-monad, providing no added safety and requiring manual memory management. The wrapped interface uses newForeignPtr
to introduce all Futhark pointers to the GC, and provides function types closer to those used within Futhark, returning tuples instead of writing to pointers.
Context Generation
getContext :: [ContextOption] -> IO Context
Available context options will depend on backend used.
The Fut monad
To make the wrappers safe, and reduce clutter from explicitly passing around the context, the Fut
monad is introduced. The Fut
monad is an environment monad that implicitly passes the context around as necessary. Like the ST
monad, the Fut
monad is parameterised by a rigid type variable to prevent references to the context from escaping the monad.
To run computations, the function
runFutIn :: Context -> (forall c. Fut c a) -> a
is used. Additionally
runFutWith :: [ContextOption] -> (forall c. Fut c a) -> a
runFut :: (forall c. Fut c a) -> a
are defined for convienience for cases where the context doesn't need to be reused.
For more flexibility, the FutT monad transformer can be used. For convenience the type synonyms
type Fut c = FutT c Identity
type FutIO c = FutT c IO
are defined, but entry-points are in the general Monad m => FutT c m
.
To run the transformer
runFutTIn :: Context -> (forall c. FutT c m a) -> m a
runFutTWith :: [ContextOption] -> (forall c. FutT c m a) -> m a
runFutT :: (forall c. FutT c m a) -> m a
For lifting
mapFutT :: (m a -> n b) -> FutT c m a -> FutT c n b
map2FutT :: (m a -> n b -> k c) -> FutT c' m a -> FutT c' n b -> FutT c' k c
pureFut :: Monad m => Fut c a -> FutT c m a
unsafeFromFutIO :: FutIO c a -> Fut c a
When using FutT c
with other transformers in a stack the type of the function running the monad may need to be defined explicitly.
In the same way as runFutT
, these signatures require an explicit forall
to force c
to be fully polymorphic.
runMyMonad :: (forall c. MyMonad c a) -> a
This requires the RankNTypes
extension.
For conversion between Futhark values and Haskell values, two classes are defined.
class Input fo ho where
toFuthark :: Monad m => ho -> FutT c m (fo c)
class Output fo ho where
fromFuthark :: Monad m => fo c -> FutT c m ho
Instances of Input and Output are generated for all transparent Futhark-arrays. The Haskell representation is Array S
from Data.Massiv.Array
. The absence of functional dependencies in the definitions might require more explicit type signatures, but gives more flexibility to define new instances. For tuples of instances, functions on the form fromFutharkTN
, where N
is the tuple size, are defined.
Memory management
All of the wrapped values have finalizers, and should eventually be garbage collected. However, GHCs GC does not know how much memory the context is using, and so collection will not always be triggered frequently enough. This is primarily an issue when the program iterates on Futhark values, without any Haskell-side allocations.
One way to deal with this is to manually manage the memory using
finalizeFO :: (MonadIO m, FutharkObject wrapped raw) => wrapped c -> FutT c m ()
As with any manual memory management, the programmer is responsible for ensuring that the finalized value will not be used afterwards. For cases where the object is used in more than one thread without synchronisation,
addReferenceFO :: (MonadIO m, FutharkObject wrapped raw) => wrapped c -> FutT c m ()
can be used. addReferenceFO
increments the reference counter of the object and finalizeFO
will just decrement this counter until it's 0
.