similar to: [LLVMdev] OCaml bindings broken in trunk

On Sep 7, 2012, at 3:40 PM, Nuno Lopes wrote: > The linking issue is a recent breakage. > I traced it back to r163175. Basically LLVMConstInlineAsm() got an additional parameter, but the C headers and the OCaml bindings were not updated accordingly. r163175 was my change. I'm not familiar with the OCaml project. If I'm responsible for updating said C headers/OCaml bindings, would

The linking issue is a recent breakage. I traced it back to r163175. Basically LLVMConstInlineAsm() got an additional parameter, but the C headers and the OCaml bindings were not updated accordingly. About the miscompilations, can you provide further details? Nuno ----- Original Message ----- > I've recently upgraded my project-local copy of LLVM from 3.1svn to the > latest

Didn't Benjamin already fix this in svn 163502? On Sep 10, 2012, at 10:08 AM, Chad Rosier <mcrosier at apple.com> wrote: > > On Sep 7, 2012, at 3:40 PM, Nuno Lopes wrote: > >> The linking issue is a recent breakage. >> I traced it back to r163175. Basically LLVMConstInlineAsm() got an additional parameter, but the C headers and the OCaml bindings were not updated

On Sep 10, 2012, at 3:34 PM, Bob Wilson wrote: > Didn't Benjamin already fix this in svn 163502? Looks that way.. > On Sep 10, 2012, at 10:08 AM, Chad Rosier <mcrosier at apple.com> wrote: > >> >> On Sep 7, 2012, at 3:40 PM, Nuno Lopes wrote: >> >>> The linking issue is a recent breakage. >>> I traced it back to r163175. Basically

Hello list, Since reading the kaleidoscope tutorial I have decided to play around with creating a language I've had in the back of my mind for some time. I would prefer not to write the front end in c or c++ though if it can be avoided. I read online that the ocaml bindings are distributed with llvm but are not always as up to date as the c or c++ bindings. Is this (still) the case? Is

I've just committed the first two chapters of my ocaml llvm bindings tutorial by porting the Kaleidoscope tutorial to ocaml. These chapters are the lexer and parser. If anyone is interest in trying it out, I'd love any feedback. If you've got the svn trunk checked out, you'll find the docs here: docs/tutorial/OCamlLangImpl1.html docs/tutorial/OCamlLangImpl2.html If not, you can

On Mon, Jul 26, 2010 at 10:15 AM, Jason Johnson <jason.johnson.081 at gmail.com> wrote: > Hello list, > > Since reading the kaleidoscope tutorial I have decided to play around with creating a language I've had in the back of my mind for some time.  I would prefer not to write the front end in c or c++ though if it can be avoided.  I read online that the ocaml bindings are

i''m the Mageia Xen package maintainer, and a user reported that i had missing symbols in my ocaml bindings: https://bugs.mageia.org/show_bug.cgi?id=5199 i''m using Xen 4.2.1 and ocaml 3.12.1 the problem is that if you just to a simple hello world and you''re using certain bindings (eg: xeneventch): you get missing symbols. (others appear to be fine). I know next to

Hi all, Starting from Chapter 4 of the Kaleidoscope tutorial (where the JIT support is added), there's some strange behaviour, ready> def foo(x y) x+y; ready> Read function definition: define double @foo(double %x, double %y) { entry: %addtmp = fadd double %x, %y ret double %addtmp } ready> foo(1, 2); ready> Evaluated to 3.000000 ready> foo(3, 4); ready> Evaluated to

I try to understand cmake build configuration. As an example, I copied Kaleidoscope from llvm examples to some other directory (e.g., /tmp/Kaleidoscope). What change(s) that I need to make to "CMakkeLists.txt" in order to build Kaleidoscope from /tmp/Kaleidoscope? Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi all, I tried to modify Kaleidoscope Tutorial (toy.cpp from llvm/examples/Kaleidoscope/Chapter7, LLVM 3.3 release branch) in order to use MCJIT instead of JIT. I get segmentation fault when running toy.cpp with fibonacci example from the tutorial. My modified toy.cpp is in attachment and still works with JIT (when #define USE_MCJIT line is commented out). I read discussions regarding

Oh - I know what this is. You were running this on Linux, right? On MacOS I think the symbol is getting double mangled while going through MCJIT::getSymbolAddress, hence the failure: The IR level foo function gets compiled to "_foo" in the object file, and then "_foo" gets mangled to "__foo" when we look it up. Linux doesn't do assembly level name-mangling, so

On Mar 27, 2008, at 04:30, Erick Tryzelaar wrote: > I've just committed the first two chapters of my ocaml llvm bindings > tutorial by porting the Kaleidoscope tutorial to ocaml. These chapters > are the lexer and parser. If anyone is interest in trying it out, I'd > love any feedback. If you've got the svn trunk checked out, you'll > find the docs here: > >

Hello all, is there any documentation for Ocaml LLVM API? I found only tutorial for Kaleidoscope which is not clear enough for me. Thanks.  -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120914/51f58269/attachment.html>

Hi Dmitri, You might want to try replacing the call to JMM->invalidInstructionCache() with a call to TheExecutionEngine->finalizeObject(). If you are getting a non-NULL pointer from getPointerToFunction but it crashes when you try to call it, that is most likely because the memory for the generated code has not been marked as executable. That happens inside finalizeObject, which also

Hi, I am building a new JIT compiler for Lua (actually a derivative of Lua), and am planning to use LLVM for this. I have trying out some basic functions using LLVM 3.5.1. I have been puzzled by one aspect of the MCJIT versions of the Kaleidoscope sample, and would hugely appreciate some insight. Can a single MCJIT instance be used to manage several modules? Why is a separate MCJIT instance

On Nov 15, 2010, at 8:42 AM, Rob Pieke wrote: > SUCCESS! > > Sorry, I had removed the addFnAttr() call by accident. Using the basicAA pass and ReadOnly, as you suggested, works like a charm! > > :) Thanks. I've updated the documentation and examples in r119169. I didn't update the OCaml documentation or examples yet. It looks like the OCaml bindings don't expose

Lang, I added the add/get global mapping to my kaleidoscope JIT, but I think perhaps these would make more sense if they were added to the object linking layer as they would be generally usable there. On Aug 19, 2015, at 11:19 PM, Andy Somogyi wrote: > Hey Lang, > > I've added this to my Kaleidoscope JIT, and it seems to work just fine, basically I copied the global mapping

Hi all, I am new to LLVM and have been working through the Kaleidoscope tutorial. Everything is working fine so far except for local externs (as opposed to things like the math functions, which are working). Note that I have seen this bug with the reference code listing, as well as my own code. link to code: https://llvm.org/docs/tutorial/LangImpl05.html#full-code-listing [c34n10 kaleidoscope]

SUCCESS! Sorry, I had removed the addFnAttr() call by accident. Using the basicAA pass and ReadOnly, as you suggested, works like a charm! :) > -----Original Message----- > From: Rob Pieke > Sent: Monday, November 15, 2010 4:40 PM > To: 'Duncan Sands' > Cc: 'llvmdev at cs.uiuc.edu'; 'Dan Gohman' > Subject: RE: [LLVMdev] Optimization of calls to