Hackage :: [Package]

llvm: Bindings to the LLVM compiler toolkit.

[ bsd3, code-generation, compilers-interpreters, deprecated, library ] [ Propose Tags ] [ Report a vulnerability ]
Deprecated in favor of llvm-hs, llvm-general, llvm-tf

High-level bindings to the LLVM compiler toolkit.

  • New in 3.2.0.0: Builds against LLVM 3.2

  • New in 3.0.0.0: The low-level bindings have been split into the llvm-base package.

  • New in 0.9.1.1: Builds against LLVM 2.9.

  • New in 0.9.1.0: Util.Memory for memory related intrinsics.

  • New in 0.9.0.0: Adapted to LLVM 2.8 (removed support for Union types).

[Skip to Readme]

Modules

[Last Documentation]

  • LLVM
    • LLVM.Core
    • LLVM.ExecutionEngine
    • Util
      • LLVM.Util.Arithmetic
      • LLVM.Util.File
      • LLVM.Util.Foreign
      • LLVM.Util.Loop
      • LLVM.Util.Memory
      • LLVM.Util.Optimize

Flags

Automatic Flags
NameDescriptionDefault
developer

operate in developer mode

Disabled

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

Downloads

Maintainer's Corner

Package maintainers

For package maintainers and hackage trustees

Candidates

  • No Candidates
Versions [RSS] 0.0.2, 0.4.0.0, 0.4.0.1, 0.4.0.3, 0.4.1.0, 0.4.2.0, 0.4.4.1, 0.4.4.2, 0.5.0.1, 0.6.0.2, 0.6.0.3, 0.6.2.0, 0.6.3.0, 0.6.4.0, 0.6.5.0, 0.6.6.0, 0.6.7.0, 0.6.8.0, 0.7.0.0, 0.7.0.1, 0.7.1.0, 0.7.1.1, 0.7.1.2, 0.8.0.2, 0.8.1.0, 0.8.2.0, 0.9.0.1, 0.9.1.0, 0.9.1.1, 0.9.1.2, 0.10.0.0, 0.10.0.1, 3.0.0.0, 3.0.1.0, 3.2.0.0, 3.2.0.1, 3.2.0.2
Change log CHANGELOG.md
Dependencies base (>=3 && <5), bytestring (>=0.9), containers, directory, llvm-base (>=3.2.0.2 && <4), mtl, process, type-level [details]
Tested with ghc ==6.12.3, ghc ==7.0.4, ghc ==7.2.2
License BSD-3-Clause
Author Bryan O'Sullivan, Lennart Augustsson
Maintainer Bryan O'Sullivan <bos@serpentine.com>, Lennart Augustsson <lennart@augustsson.net>
Category Compilers/Interpreters, Code Generation
Home page https://github.com/bos/llvm
Bug tracker https://github.com/bos/llvm/issues
Source repo head: git clone git://github.com/bos/llvm.git
head: hg clone https://bitbucket.org/bos/llvm/
Uploaded by CarterSchonwald at 2013-05-28T00:59:47Z
Distributions
Reverse Dependencies 5 direct, 59 indirect [details]
Downloads 28192 total (87 in the last 30 days)
Rating (no votes yet) [estimated by Bayesian average]
Your Rating
  • λ
  • λ
  • λ
Status Docs not available [build log]
All reported builds failed as of 2016-12-21 [all 9 reports]

Readme for llvm-3.2.0.2

[back to package description]

Haskell LLVM bindings

This package provides Haskell bindings for the popular LLVM compiler infrastructure project.

Compatibility

We try to stay up to date with LLVM releases. The current version of this package is compatible with LLVM 2.9 and 2.8. Please understand that the package may or may not work against older LLVM releases; we don't have the time or resources to test across multiple releases.

Configuration

By default, when you run cabal install, the Haskell bindings will be configured to look for LLVM in /usr/local.

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

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.

Staying in touch

There is a low-volume mailing list named haskell-llvm@projects.haskellorg. If you use the LLVM bindings, you should think about joining.

If you want to contribute patches, please clone a copy of the git repository:

git clone git://github.com/bos/llvm

Patches are best submitted via the github "pull request" interface.

To file a bug or a request for an enhancement, please use the github issue tracker.