The llvm package

[Tags:bsd3, deprecated, library]
Deprecated. in favor of llvm-general

Bindings to the LLVM compiler toolkit

[Skip to Readme]


Versions 0.0.2,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Dependencies base, bytestring (>=0.9), directory, mtl, process [details]
License BSD3
Author Bryan O'Sullivan, Lennart Augustsson
Maintainer Bryan O'Sullivan <>, Lennart Augustsson <>
Category Compilers/Interpreters, Code Generation
Home page
Uploaded Sun Jan 25 22:56:14 UTC 2009 by LennartAugustsson
Distributions Debian:, NixOS:
Downloads 8031 total (7 in the last 30 days)
0 []
Status Docs uploaded by user
Build status unknown [no reports yet]




bytestring-in-basebytestring was part of the base library in ghc-6.6 days. The bytestring low level interface is in Data.ByteString.Internal and Data.Bytestring.Unsafe not Data.ByteString.BaseEnabledAutomatic

Use -f <flag> to enable a flag, or -f -<flag> to disable that flag. More info


Maintainer's Corner

For package maintainers and hackage trustees

Readme for llvm

Readme for llvm-

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 "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 directory.

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

  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