Andrew Anderson

@scuellar I got to the bottom of this today. As it turns out, we can bind to the C++ metadata just fine, but llvm-hs supports only a restricted subset of...

Commit b518fe11241e8aea40760eee9cd95421ef772646 introduces a change to the behaviour of llvm-hs upon encountering an unhandled `DINode` type. Instead of crashing, we now just ignore the `DINode`, but the plumbing is in...

There are also places where we have an awkward division between our C/C++ code and Haskell. For example, there are many instances where we have FFI wrapper functions written in...

Thanks for the report! This looks like a simple bug in the tests -- instead of hardcoding the native target triple, we should be asking `llvm-config --host-target` what it is...

This is actually very straightforward to do, because LLVM exposes this through the C API: https://llvm.org/doxygen/group__LLVMCTarget.html However, I don't quite understand exactly what you mean by "not being able to...

Ah, I see. I was only thinking about datatypes that LLVM provides, but a tagged union is indeed tricky. You would need to iterate over the union types and statically...

@luc-tielen I understand what you want to do, but I don't think it's possible with `llvm-hs` right now, so you're correct to post under this issue. LLVM wants you to...

@luc-tielen mixing and matching between the high-level `llvm-hs-pure` and low-level `llvm-hs` FFI interface directly in this way is uncharted territory, but it makes sense that builtin types should always be...

@cartazio if you're still feeling like doing some work on this the initial implementation by @cocreature has been merged on the llvm-12 branch, and there is some code in llvm-hs-examples...

@jrp2014 unfortunately that's a familiar story where the state of LLVM documentation is concerned :( I've been doing a lot of work recently with the sanitizers, and 99% of the...