sellout/cl-llvm

CFFI bindings for LLVM

• 🔭 I’m currently working on GHC plugins & category theory modeling
• 🌱 I’m currently learning enriched category theory and dependent type theory
• 👯 I’m looking to collaborate on writing about functional programming
• 💬 Ask me about freediving
• 📫 How to reach me: @sellout on Mastodon.social
• 😄 Pronouns: they/them
• ⚡ Fun fact: I can hold my breath for four minutes.

cl-llvm's Issues

memory-fault-error with dispose-module after dispose-execution-engine

http://stackoverflow.com/questions/27103943/llvm-api-correct-way-to-create-dispose

and

(with-objects ((m module "sample")
               (e execute-engine m))
  ...)

will cause the error.

depends on CCL for converting arrays

We use ccl:make-heap-ivector to convert lisp sequences to C arrays. We need this to be more portable.

Having trouble loading the system

Command: (asdf:load-system 'kaleidoscope)
This is the error I'm getting:
Unable to load any of the alternatives: ("libLLVM.so" "libLLVM.so.1" "libLLVM-3.6.so" "libLLVM-3.1.so" "libLLVM-3.1.so.1" "libLLVM-3.1svn.so" "libLLVM-3.1svn.so.1" "libLLVM-3.0.so" "libLLVM-3.0.so.1") [Condition of type CFFI:LOAD-FOREIGN-LIBRARY-ERROR]

array conversion only works for `(signed-byte 64)`

We need to make the type of the ivector dependent on the value-type of the carray. The nicest way to do this would be if CFFI exposed some way to get the lisp type that a given C type would be converted into.

need access to static functions in Target.h

LLVMInitializeAllTargetInfos, LLVMInitializeAllTargets, and LLVMInitializeNativeTarget are all static, and therefore don’t exist in the DLL. So we can’t use them from Lisp. But they are necessary for setting up a JIT.

comments are broken in Kaleidoscope

If you try to insert a comment, you end up in an infinite loop of “error: unknown token when expecting an expression”

Support for LLVM 3.5

Hey,

In case anyone needs help compiling this for LLVM 3.5, you will have to remove the line

((:linker-private-weak-auto "LLVMLinkerPrivateWeakDefAutoLinkage"))

from grovel.lisp. After you've done that, it works just fine (at least on OS X with SBCL).

make-jit-compiler cause memory fault error.

Tutorial raise error

Tutorial in Common Lisp includes this kind of code

(llvm:with-objects ((*builder* 'llvm:builder))
  ...)

, and this can raise error, because with-objects will be expanded into

(llvm:with-object (*builder* 'llvm:builder)
  ...)

, and the argument placed in 'llvm:builde should be (OR (VECTOR CHARACTER) (VECTOR NIL) BASE-STRING SYMBOL CHARACTER), not (QUOTE SYMBOL).

Though I can fix it in a few minutes, I have to ask which one will suite

(llvm:with-object (*builder* 'llvm:builder)
  ...)

;; or
(llvm:with-object (*builder* llvm:builder)
  ...)

“ready> ” prompt prints too often

We get double prompts on each input, and there seem to be prompts with a lot of outputs, as well.

Hard to build on Debian 8 - required llvm libraries are too old?

Log: http://report.quicklisp.org/2016-01-11/failure-report/cl-llvm.html#llvm

library function definitions don't work

I've defined the library functions using CFFI:DEFCALLBACK, but that isn't actually what we want – IE, they don't work.

DISPOSE-MODULE causes SIGBUS

LLVMDisposeModule is causing a SIGBUS whenever it is called. The workaround is to just let modules leak for now, but this will have to be sorted out.

get required patches merged into CFFI