similar to: [LLVMdev] llvm-fs 0.0.0

Hello All, I'm building an F# binding for LLVM and it seems to be working for the parts of Core and BitWriter that I've tested but I've hit problems with Target/ExecutionEngine. The following test code works with the initializeNativeTarget line commented out like so: <https://github.com/keithshep/llvm-fs/blob/b7050b841108dc703e58563a4cff8845603c950d/test/simpletest2.fs> ...

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

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

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

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

Anton wrote: > > 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? I followed both those instructions and (separately) the instructions from the LLVM "Getting Started with

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

Hi, Does any documentation exist (or maybe could someone give an overview) on what kind of stuff we're missing out on by binding to the C API? I'd be really interested to know. Thank you, Keith On Mon, May 14, 2012 at 3:39 AM, Duncan Sands <baldrick at free.fr> wrote: > Hi Mikael, > >>     2. LLVM.NET/LLVM-F# <http://LLVM.NET/LLVM-F#> uses the C API.  Are there

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

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

Hello, Most of the functions in the C api that take a string arg don't require a string length but some do (eg. the somewhat new MD functions). Is there a reason that some functions ask for length? If possible, I'd prefer for the API not to require length for reasons of simplicity and consistency and if it turns out that there is consensus for this change I'm happy to prepare a patch.

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

On Thu, Jun 16, 2011 at 01:02:21PM +0300, C?neyt Sina Koca wrote: > Since the code im trying to gave this error : > > ImportError: /usr/lib/pymodules/python2.6/libguestfsmod.so: undefined > symbol: PyCapsule_New > > I copied this libguestfsmod.so.0.0.0 > from python-libguestfs-1.9.10-1.1.x86_64.rpm package and the code works fine > now. > > When I compared the

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

Hi Mikael, > 2. LLVM.NET/LLVM-F# <http://LLVM.NET/LLVM-F#> uses the C API. Are there > anything important missing from this API, things that are only accessible > through the C API? there's lots missing from the C API because functionality is added when someone needs it. In the other direction, there's nothing the C binding can do that the C++ API can't as far as

Hi, I have decided against coding my planned Braceless compiler in C++ and have instead opted for using the .NET bindings that Keith Shephard have made using F# (a .NET language). This leads to two questions: 1. Is it okay if I adapt the Kalaidoscope tutorial to C# and we include the adapted version in the LLVM.NET distro and on the LLVM.NET website? I have written very clearly that Chris

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

The latest release of the CIL C frontend (http://sf.net/projects/cil) now includes a module to generate LLVM assembly code from CIL's intermediate format. It should be considered alpha-level code and still has a number of significant limitations: It is targeted to the 32-bit mode of x86 processors using gcc's C dialect. It handles all of C, except: - bitfields - inline

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,