The llvm package

[ Tags: bsd3, code-generation, compilers-interpreters, deprecated, library ] [ Propose Tags ]
Deprecated. in favor of llvm-general

Bindings to the LLVM compiler toolkit. * New in Adapted to LLVM 2.8 (removed support for Union types);

[Skip to Readme]


Versions 0.0.2,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Dependencies base (>=3 && <5), bytestring (>=0.9), directory, mtl, process, type-level [details]
License BSD3
Author Bryan O'Sullivan, Lennart Augustsson
Maintainer Bryan O'Sullivan <>, Lennart Augustsson <>
Category Compilers/Interpreters, Code Generation
Home page
Bug tracker Lennart Augustsson <>
Source repo head: darcs get
Uploaded Sat Nov 6 05:14:45 UTC 2010 by BryanOSullivan
Distributions Debian:, NixOS:
Downloads 12816 total (213 in the last 30 days)
Rating (no votes yet) [estimated by rule of succession]
Your Rating
  • λ
  • λ
  • λ
Status Docs uploaded by user
Build status unknown [no reports yet]
Hackage Matrix CI




Maintainer's Corner

For package maintainers and hackage trustees

Readme for llvm-

[back to package description]
Haskell LLVM bindings

This package provides Haskell bindings for the popular LLVM compiler
infrastructure project.  If you don't know what LLVM is, the main LLVM
home page is here:


By default, when you run "cabal install" or "runghc Setup configure",
the Haskell bindings will be configured to install to /usr/local.  The
configure script will look for your LLVM installation in that same

If you have LLVM installed in a different location, e.g. /usr, you can
tell the configure script where to find it as follows:

  cabal install --configure-option=--with-llvm-prefix=/usr

  runghc Setup configure --configure-option=--with-llvm-prefix=/usr

Package status - what to expect

This package is still under development.

The high level bindings are currently incomplete, so there are some
limits on what you can do.  Adding new functions is generally easy,
though, so don't be afraid to get your hands dirty.

The high level interface is mostly safe, but the type system cannot
protect against everything that can go wrong, so take care.  And, of
course, there's no way to guarantee anything about the generated code.

Jump in and help!

We welcome your comments and contributions.  You can send email to us
at <> or <>.  If you want to
send patches, please get a copy of the darcs repository:

  darcs get