Displaying 6 results from an estimated 6 matches for "llvmwritebitcodetofil".
Did you mean:
llvmwritebitcodetofile
2010 Nov 09
0
[LLVMdev] linking error in LLVM C bindings.
Well, now I've got another problem. When I actually connect things up
to *use* the binding library I built, I run into an unresolved symbol
error with respect to the function LLVMWriteBitcodeToFile().
The assembly dump showing that my library does have that function follows:
> eli at eli-netbook:~/Programs/decac$ objdump -d
> src/jllvm/llvm/libjllvm.so | grep LLVMWriteBitcodeToFile
> 0055cd54 <LLVMWriteBitcodeToFileHandle at plt>:
> 0058c504 <LLVMWriteBitcodeToFile at...
2014 Dec 02
3
[LLVMdev] Questions about deallocation responsibilities
I am, from a front end, calling functions like LLVMModuleCreateWithName, found
in Core.h, ultimately calling LLVMWriteBitcodeToFile, found in BitWriter.h.
Do I correctly presume, from the existence of LLVMDisposeModule, that
I am responsible for calling it when I'm done? Will I need to do deeper
disposing myself? I presume at least I will need to free strings I allocated
myself, such as the module name I passed in.
Wha...
2017 Jan 25
2
mcjit C interface problems
...ToInt(args[0], 0));
printf("args[1]: %d\n", (int)LLVMGenericValueToInt(args[1], 0));
LLVMGenericValueRef res = LLVMRunFunction(engine, sum, 2, args);
printf("result: %d\n", (int)LLVMGenericValueToInt(res, 0));
LLVMDumpModule(mod);
// Write out bitcode to file
if (LLVMWriteBitcodeToFile(mod, "sum.bc") != 0) { fprintf(stderr, "error
writing bitcode to file, skipping\n"); }
LLVMDisposeBuilder(builder);
LLVMDisposeExecutionEngine(engine);
}
Here's what I see when I run it:
$ ./capi_test 5 6
args[0]: 5
args[1]: 6
result: 5
; ModuleID = 'my_module'...
2015 Oct 17
3
The future of LLVM's C APIs: Notes and BoF.
(Moving this to llvm-dev)
On Friday, October 16, 2015, Justin Bogner <mail at justinbogner.com> wrote:
> Some users of llvm-c want stable API interfaces into various parts of
> the LLVM infrasture, others want further ABI guarantees about this
> usage, and still others simply want a way to bind to LLVM through their
> language frontend’s existing FFI support for C.
>
> If
2015 Oct 22
2
The future of LLVM's C APIs: Notes and BoF.
...ity are working on splicing a
> llvm back end onto our Modula3 compiler front end. We have zero-thickness
> bindings written in Modula3 which match C bindings like core.h. In our
> front
> end executable, we only build llvm IR in memory, then use
> LLVMPrintModuleToFile
> and/or LLVMWriteBitcodeToFile. We only link in the needed parts of the
> llvm
> infrastructure to build and write the llvm IR. Then we run stock llc on
> the
> IR code in the emitted file.
>
> We have had to write an additional binding to DIBuilder for this purpose,
> as well as to a few odd other C++ fu...
2007 Oct 10
1
[LLVMdev] make check fails on latest SVN version
...to 'char*'
/tmp/camlprim8cfa59.c:821: warning: deprecated conversion from string
constant to 'char*'
/home/edwin/llvm-svn/llvm/Release/lib/ocaml/libllvm_bitwriter.a(bitwriter_ocaml.o):
In function `llvm_write_bitcode_file':
bitwriter_ocaml.c:(.text+0x5): undefined reference to `LLVMWriteBitcodeToFile'
collect2: ld returned 1 exit status
Error while building custom runtime system
FAIL: /home/edwin/llvm-svn/llvm/test/Bindings/Ocaml/vmcore.ml
Failed with exit(2) at line 1
while running: /usr/bin/ocamlc -cc g++ -I
/home/edwin/llvm-svn/llvm/Release/lib/ocaml llvm.cma llvm_analysis.cma
llvm_bit...