https://github.com/huonw/llvmint

https://github.com/huonw/llvmint

Last synced: about 1 month ago
JSON representation

• Host: GitHub
• URL: https://github.com/huonw/llvmint
• Owner: huonw
• License: apache-2.0
• Created: 2015-01-19T05:41:52.000Z (almost 10 years ago)
• Default Branch: master
• Last Pushed: 2015-05-01T14:33:45.000Z (over 9 years ago)
• Last Synced: 2023-04-10T09:39:41.943Z (over 1 year ago)
• Language: Rust
• Homepage: http://huonw.github.io/llvmint/llvmint/
• Size: 2.08 MB
• Stars: 25
• Watchers: 4
• Forks: 7
• Open Issues: 5
• Metadata Files:
  • Readme: README.md
  • License: LICENSE-APACHE

Awesome Lists containing this project

README

        
# LLVMint

Raw Rust bindings to (essentially) all LLVM intrinsics. This library

does little to protect you against using intrinsics on platforms they

don't support and generally doesn't do any error checking.

The bindings in this lib are autogenerated from the LLVM sources, so

LLVM crashes caused by using it are likely to be due to misuses or

insufficiently specific target-cpu/target-feature directives rather

than the library itself (although it is of course possible for the

library to have bugs too).

This is highly experimental and currently just pins to whatever

version of LLVM works for me. I'll look into better versioning more

seriously if rustc starts sticking to released versions of LLVM, and

once I'm more happy with the experimentation.

## Regenerating

To (re)create the table of intrinsics `allintrinsics`:

```sh

# directory containing a rust-lang/rust checkout

RUST=~/rust

cat ${RUST}/src/llvm/include/llvm/IR/Intrinsics*.td > allintrinsics

```

To recreate the library file:

```sh

cd generator

cargo build --release

./target/release/generator < ../allintrinsics > ../src/lib.rs

```

Why not a build script? Partly because I haven't written one, partly

because I don't want to require users to have access to the info

necessary from LLVM, so just checking the output into VC is easy.