search for: llvmmodulecreatewithnam

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...

...bby language I am making. I have experimented with the C bindings since the project is written in C. I had no problems building a single lllvm module so far. I am not using a JIT compiler but at least at the moment am simply generating executables. The workflow I am using is to build a module with LLVMModuleCreateWithName() and populate it with the LLVMBuilder. After everything is in the module I simply output it into a file with LLVMPrintModuleToFile(). Then I am calling llc to convert the IR to native machine code and finally gcc to create an executable out of it. All these from inside my program. It may not be...

...king. I have > experimented with the C bindings since the project is written in C. I had > no problems building a single lllvm module so far. I am not using a JIT > compiler but at least at the moment am simply generating executables. The > workflow I am using is to build a module with LLVMModuleCreateWithName() > and populate it with the LLVMBuilder. > > > > After everything is in the module I simply output it into a file with > LLVMPrintModuleToFile(). Then I am calling llc to convert the IR to native > machine code and finally gcc to create an executable out of it. All these &gt...

...Compiler(&engine, provider, 3, &error); $ llvm-gcc `llvm-config --cflags` -c fac.c $ g++ `llvm-config --libs --cflags --ldflags core analysis executionengine jit interpreter native backend engine` fac.o -o fac fac.o: In function `main': c:\Work\llvm//fac.c:20: undefined reference to `LLVMModuleCreateWithName' c:\Work\llvm//fac.c:21: undefined reference to `LLVMInt32Type' c:\Work\llvm//fac.c:22: undefined reference to `LLVMInt32Type' c:\Work\llvm//fac.c:22: undefined reference to `LLVMFunctionType' c:\Work\llvm//fac.c:22: undefined reference to `LLVMAddFunction' c:\Work\llvm//fac.c:...

you want to use the execution engine and JIT but do not put them in the llvm-config line?? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20091106/d26a0a02/attachment.html>

I'm trying to use LLVM on Windows for the first time. Keith Sheppard has published some F# bindings: https://github.com/keithshep/llvm-fs They require an LLVM-3.0.dll file. I'm not familiar with Windows but I think I've managed to build LLVM 3.0 using both VS2010 and Cygwin but neither build seems to have produced said file. The VS2010 build (made using CMake) seems to have made

> I'm trying to use LLVM on Windows for the first time. Keith Sheppard has > published some F# bindings: > >  https://github.com/keithshep/llvm-fs Keith specified the build instructions there, what were the problems of using them? -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

...dio" page but neither seems to have produced the file I need. Following those instructions, I get .a files and no .dll files so the llvm-fs bindings do not work because they expect to bind to an LLVM-3.0.dll file. For example: [<DllImport("LLVM-3.0.dll", EntryPoint="LLVMModuleCreateWithName")>] extern void* (* LLVMModuleRef *) moduleCreateWithNameNative( string ModuleID) let moduleCreateWithName _ModuleID = new ModuleRef (moduleCreateWithNameNative (_ModuleID)) When I try to run an example I get "Unable to load DLL 'LLVM-3.0.d...

...# craps w/ following: http://pastie.textmate.org/private/t33luliw4mdf7l2zkj8hg Is that supposed to work? I also tried creating a Function w/ ExternalLinkage calling LLVM C API function with no success: Function *f = Function::Create(type, Function::ExternalLinkage, StringValuePtr("LLVMModuleCreateWithName"), module); Any pointer or explication would be greatly appreciated, thanks a lot, - ma

...LLVMBuildRet(builder, returnVal); LLVMDisposeBuilder(builder); return result; } int main (int argc, const char * argv[]) { NSAutoreleasePool * pool = [[NSAutoreleasePool alloc] init]; char * error = NULL; LLVMExecutionEngineRef engine; LLVMModuleRef module = LLVMModuleCreateWithName("MyModule"); LLVMValueRef toCall = d(module); LLVMDumpModule(module); LLVMLinkInInterpreter(); LLVMCreateInterpreterForModule(&engine, module, &error); LLVMGenericValueRef result = LLVMRunFunction(engine, toCall, 0, NULL); LLVMDisp...

Hi, I'm attempting to use MCJIT with the C interface with llvm-3.9.0, and it doesn't seem to work. This code is derived from Paul Smith's example code: int main(int argc, char const* argv[]) { LLVMModuleRef mod = LLVMModuleCreateWithName("my_module"); LLVMTypeRef param_types[] = {LLVMInt32Type(), LLVMInt32Type()}; LLVMTypeRef ret_type = LLVMFunctionType(LLVMInt32Type(), param_types, 2, 0); LLVMValueRef sum = LLVMAddFunction(mod, "sum", ret_type); LLVMBasicBlockRef entry = LLVMAppendBasicBlock(sum, &qu...

I noticed that the ocaml compilation isn't using the .opt executables if they're available. We might gain a slight optimization in ocaml compile time by optionally using them with this patch. --- autoconf/configure.ac | 18 +++++ configure | 195 ++++++++++++++++++++++++++++++++++++++++++------ 2 files changed, 188 insertions(+), 25 deletions(-) -------------- next part

...ryBuffer *LLVMMemoryBufferRef; > > @@ -165,18 +165,21 @@ void LLVMDisposeMessage(char *Message); > /*===-- Modules > -----------------------------------------------------------===*/ > > /* Create and destroy modules. */ > +/** See [llvm::Module::Module]. */ > LLVMModuleRef LLVMModuleCreateWithName(const char *ModuleID); > + > +/** See [llvm::Module::~Module]. */ > void LLVMDisposeModule(LLVMModuleRef M); > > -/* Data layout */ > +/** Data layout. See [Module::getDataLayout]. */ > const char *LLVMGetDataLayout(LLVMModuleRef M); > void LLVMSetDataLayout(LLVMModuleRef M...

--- bindings/ocaml/llvm/llvm.ml | 2 +- bindings/ocaml/llvm/llvm.mli | 2 +- bindings/ocaml/llvm/llvm_ocaml.c | 2 +- include/llvm-c/Core.h | 32 +++++++++++++++++++------------- 4 files changed, 22 insertions(+), 16 deletions(-) -------------- next part -------------- A non-text attachment was scrubbed... Name: 316a84e85ed2363551149e65a227c8e7c8192624.diff Type:

Attached is what I got thus far. What I'm struggling with is proper integration in build system. What is in there is just wild guesses from my side, both on autoconf and cmake variants. It would be great if someone with proper knowledge of the buildsystems could have a look. Also I'm not sure how to properly handle compilation on msvc - clearly "-std=c11 -Wstrict-prototypes" is