search for: llvmorcgetsymboladdress

Displaying 5 results from an estimated 5 matches for "llvmorcgetsymboladdress".

2019 Feb 25
2
LLVM C API OrcJIT
Hello, I've been trying to use LLVM's Orc JIT from C API for a few days and i can't get it to work, I'm kind of annoyed for the lack of documentation examples for the C API. Here's my code: https://hasteb.in/ohexiweb.cpp I compile it using clang `llvm-config --cflags --ldflags --libs all` main.c -o main -g -rdynamic And it ends up segfaulting at the line where it calls
2018 Mar 14
0
LLVM ORC JIT API
...lse would be sufficient. Also, which OS and which version of LLVM do you use? > On 14. Mar 2018, at 10:17, Wycliff Bironga <wycliffb at gmail.com> wrote: > > I only use the LLVMOrcJITStackRef from the C API. I convert my ast > into IR then add it to the ORC layer. I use the > LLVMOrcGetSymbolAddress function to resolve ORC symbols. I can't > really use the C++ API for my design. > > On 13/03/2018, Alex Denisov <1101.debian at gmail.com> wrote: >>> Any assistance? >> >> Yes, with pleasure. >> Could you please share more details about your setup? &...
2018 Mar 13
2
LLVM ORC JIT API
I can't seem to get an external function to my IR be resolved after declaring it with external linkage. Its segfaulting. Using mingw32 qt and the C API for LLVM. Trying to interpret it fails saying program used an unknown external function. Any assistance?
2020 Jan 17
6
ORC JIT Weekly #1
Hi All, In the interests of improving visibility into ORC JIT development I'm going to try writing weekly status updates for the community. I hope they will provide insight into the design and state of development of LLVM's JIT APIs, as well as serving as a convenient space for discussions among LLVM's large and growing community of JIT API users. The length and detail will vary
2020 Jan 28
2
ORC JIT Weekly #1
...linux distros), the API churn can be > serious problem. It's fine if the set of "somewhat stable" C APIs > doesn't provide all the possible features, though. > > It's easy enough to add a bunch of wrappers or ifdefs hiding some simple > signature changes, e.g. LLVMOrcGetSymbolAddress adding a parameter as > happened in LLVM 6, but backpatching support for a larger API redesigns, > into stable versions, is scary. We do however quickly get complaints if > a supported version cannot be compiled due to dependencies, as people > tend to upgrade their OS separately from...