search for: llvmbuildgep3

.../might/ be able to manage - because we'll probably > have to keep typed pointer information around for old bitcode > deserialization. (but it does make the API awkward - when we finally do > remove LLVMBuildGEP, do we rename LLVMBuildGEP2? Do we leave it there? & > then we need LLVMBuildGEP3, etc, as things evolve?)) > > LLVMBuildTypedGEP or something and we can be done with it. When The old way is not supported anymore, LLVMBuildGEP can be removed, and eventually recycled if the need arise. > Also this works for writing, but not for reading - if code was expecting > to r...

As someone who used the LLVM C API for an experiment back in 2009ish (porting the SBCL lisp compiler to target LLVM as a backend -- never finished), I thought it was great that LLVM provided the C API. I was sad that it wasn't properly updated to include support for all the newly introduced IR features, though. (E.g. atomics). I tried to send patches for some of that stuff a while later, but