similar to: [LLVMdev] LLVMInitializeNativeTarget error

Hi, when building llvm as a shared library LLVMInitializeNativeTarget and co. (located in llvm/Support/TargetSelect) will not get exported as symbol into the shared library, because they are static inline. Since they are functions defined in the C API no one else inside LLVM calls them, which results in them not being exported. This is, of course, no problem for C programs using the C API,

Hi All, I tried build a version of LLVM pulled from the git repo on my raspberry pi. I got close to the finish line then: llvm[2]: Building Debug+Asserts Archive Library libLLVMDebugInfo.a make[2]: Leaving directory `/home/pi/llvm-git/lib/DebugInfo' make[1]: Leaving directory `/home/pi/llvm-git/lib' make[1]: Entering directory `/home/pi/llvm-git/tools/llvm-shlib' llvm[1]: Linking

On 01.09.2012, at 15:02, Keith Sheppard <keithshep at gmail.com> wrote: > Hi All, > > I tried build a version of LLVM pulled from the git repo on my > raspberry pi. I got close to the finish line then: > > llvm[2]: Building Debug+Asserts Archive Library libLLVMDebugInfo.a > make[2]: Leaving directory `/home/pi/llvm-git/lib/DebugInfo' > make[1]: Leaving

This looks great! One hitch though: it looks like I can monitor files by name but what I really want to watch is a whole directory "/llvm/trunk/include/llvm-c". I didn't see any way to do that. Do you have any idea if that is possible? I can add a rule for each file which is probably OK but then I'll miss any new files. Best, Keith On Wed, Oct 17, 2012 at 2:25 PM, Sean Silva

Dear LLVM devs (and other subscribers), when building llvm as a shared library (so or dll, tested with both) and then performing objdump on the resulting library will reveal that LLVMInitializeNativeTarget does not get exported ("objdump -x libLLVM-3.3svn.so | grep LLVMInitializeNativeTarget" will return without any output). As far as I can tell this is because the function is

Hello, I didn't see any section on this site for LLVM language bindings. There is http://llvm.org/ProjectsWithLLVM/ but that seems to be more about self-contained applications of LLVM. I think it would be useful to add a page (or section to an existing page) if you all agree. My binding is https://github.com/keithshep/llvm-fs and I know that there are many others. Best, Keith

Hi All, I've created the first tagged version of my LLVM F# bindings (0.0.0) at https://github.com/keithshep/llvm-fs. I basically created this so that I can write an F# based CIL compiler but I hope it's useful to others. Comments and bug reports are welcome. BTW it was very useful to me that the C API was structured in a nice, consistent way. It allowed me to autogen most of the

It seems that a client application needs to call InitializeNativeTarget or LLVMInitializeNativeTarget before doing any JITting. Unfortunately, LLVMInitializeNativeTarget is defined static inline and does not appear in the .a files; thus a client not written in C or C++ trying to JIT cannot link to the library and call LLVMInitializeNativeTarget that way. It can call a target-specific library

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

Hello Everyone > bindings. There is http://llvm.org/ProjectsWithLLVM/ but that seems to > be more about self-contained applications of LLVM. I think it would be > useful to add a page (or section to an existing page) if you all > agree. My binding is https://github.com/keithshep/llvm-fs and I know > that there are many others. +1. Keith, if you'll create such page including

Yes, that was my (maybe wrong) assumption. -Keith On Thu, Oct 18, 2012 at 9:33 AM, Tim Northover <t.p.northover at gmail.com> wrote: > On Thu, Oct 18, 2012 at 2:09 PM, Keith Sheppard <keithshep at gmail.com> wrote: >> This looks great! One hitch though: it looks like I can monitor files >> by name but what I really want to watch is a whole directory >>

Hello, a few days ago, I was trying to access the LLVM target registry via the LLVM-C interface. Unfortunately I can't seem to get some useful information out of it. Despite the fact that the following code is written in Pascal, can you please tell me if I have done something wrong here? // initialize all targets / target information LLVMInitializeAllTargets; LLVMInitializeAllTargetInfos;

Oops, missed initializing some stuff. Added: LLVMLinkInMCJIT(); LLVMInitializeNativeTarget(); LLVMInitializeNativeAsmPrinter(); LLVMInitializeNativeAsmParser(); Now it crashes in LLVMGetFunctionAddress(). Hmm. On Wed, Mar 8, 2017 at 5:14 PM, Toshiyasu Morita <toshi at tensyr.com> wrote: > Made it a bit further. Here's the current code: > >

> 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

On Thu, Oct 18, 2012 at 2:09 PM, Keith Sheppard <keithshep at gmail.com> wrote: > This looks great! One hitch though: it looks like I can monitor files > by name but what I really want to watch is a whole directory > "/llvm/trunk/include/llvm-c". I didn't see any way to do that. Do you > have any idea if that is possible? I can add a rule for each file > which is

Hi all, I have some code that uses the x86 JIT via the C bindings that I'm trying to migrate from targeting LLVM 2.5 to the top of tree, but I'm running into a linking problem I can't figure out. Here's how I'm invoking the JIT in 2.5. LLVMInitializeNativeTarget(); <-- for the updated version LLVMCreateMemoryBufferWithContentsOfFile("code.bc", &buffer,

I've been struggling to get LLVM to work from .NET using the llvm-fs bindings for the past few weeks. I finally found an installation procedure that works and documented it here: http://fsharpnews.blogspot.com/2012/03/using-llvm-from-f-under-windows.html The good news is that I have that program compiling the Fibonacci function and executing it from F# all via LLVM. However, I still have a

On Sat, May 11, 2013 at 01:48:44PM +0200, Christian Budde wrote: > Hello, > > a few days ago, I was trying to access the LLVM target registry via the > LLVM-C interface. Unfortunately I can't seem to get some useful > information out of it. > > Despite the fact that the following code is written in Pascal, can you > please tell me if I have done something wrong here?

Am 13.05.2013 16:16, schrieb Tom Stellard: > On Sat, May 11, 2013 at 01:48:44PM +0200, Christian Budde wrote: >> Hello, >> >> a few days ago, I was trying to access the LLVM target registry via the >> LLVM-C interface. Unfortunately I can't seem to get some useful >> information out of it. >> >> Despite the fact that the following code is written in

On Aug 12, 2010, at 10:43 AM, F van der Meeren wrote: > Where am I going wrong here? > Did you link against the library that contains the function? -eric