similar to: [LLVMdev] Calling C++ from LLVM Asm via JIT

----- Original Message ---- > From: Eli Friedman <eli.friedman at gmail.com> > To: Samuel Crow <samuraileumas at yahoo.com> > Cc: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> > Sent: Monday, August 31, 2009 3:49:01 PM > Subject: Re: [LLVMdev] accessing a bitcode library exported from C++ using the JIT > > On Mon, Aug 31, 2009 at 12:17 PM, Samuel

On Tue, Sep 1, 2009 at 4:53 AM, Samuel Crow<samuraileumas at yahoo.com> wrote: > We're using the LLVM Value * class functions to box and unbox values and functions for our stack.  The stack needs to be able to take indexing without changing the stack pointer so we're using a std::vector for that.  The std::string section would be a lot easier to replace than the two I just

Hello OvermindDL1, We are implementing an extensible language. That's one where you can add commands and constructs to the language without having to recompile the parser. We want compilation of the parser in order to "freeze" it but only as an option. One goal is to eventually get the macro functions of our language to the point where they are equivalent to the template

On Mon, Aug 31, 2009 at 12:17 PM, Samuel Crow<samuraileumas at yahoo.com> wrote: > Hello, > > My partner and I am making a small app needs to access a C++ library from the LLVM 2.5 JIT.  We've made sure that there are no classes and have put 'extern "c"' in front of the functions we need to access.  In order to make this work, we seem to need to have a bitcode

----- Original Message ---- > From: Óscar Fuentes <ofv at wanadoo.es> > To: Samuel Crow <samuraileumas at yahoo.com> > Cc: Óscar Fuentes <ofv at wanadoo.es>; LLVM Developers Mailing List ><llvmdev at cs.uiuc.edu> > Sent: Fri, January 14, 2011 4:39:57 PM > Subject: Re: Circular Deps from CMake build using makefile > > Samuel Crow <samuraileumas

Hi Chris, I was thinking that CreateValueName() was the way to add a symbol to a symbol table. Perhaps I'm thinking about this wrong. Here's what I've got: I've got a string generated by the parser which is constant. I need to add it to the symbol table so that, on starting the second pass of my compiler, I can dump all of the string constants to be generated as code. I

Hello Óscar, This time the autotools version of LLVM trunk build with Clang trunk compiled in Debug+Asserts mode without complaint with --enable-bindings=none. I suspect this makes something fishy looking with the CMake build. Do you need logfiles from configure? Thanks again, --Sam ----- Original Message ---- > From: Óscar Fuentes <ofv at wanadoo.es> > To: Samuel Crow

Hello Óscar, The single-threaded build failed the same place as the double threaded build failed which is the same place I just indicated in my previous post. The ../llvm/configure script version failed with OCaml building with about 600 assembler errors since I built it in AMD64 mode. (Oops.) Should I disable OCaml from the configure script and try again? Assembler error, input left in

On Mon, Aug 31, 2009 at 6:23 PM, Samuel Crow<samuraileumas at yahoo.com> wrote: > If you're wondering why we're doing an interpreted PEG parser generator rather than Boost Spirit 2.x, it's because we need it to be easier to debug the parser.  Once the parser is debugged it can be fed into a compiled parser generator and "frozen" into stand-alone parser code. You do

Hello Anton, Our main.bc was generated with the following command line: llvm-g++ -Illvm\include -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -c -emit-llvm -omain.bc main.cpp The amos.bc file was generated by our experimental llvm-peg parser generator whose internal workings are assembled internally using LLVM Assembly. The parser generator links a C++ library bitcode with C bindings called

Samuel Crow <samuraileumas at yahoo.com> writes: > This time the autotools version of LLVM trunk build with Clang trunk compiled in > Debug+Asserts mode without complaint with --enable-bindings=none. I suspect > this makes something fishy looking with the CMake build. Do you need logfiles > from configure? I'm clueless about what's happening there. The cyclic

Hi Sam, Thanks for your reply. I am implementing my research (http://www.it.usyd.edu.au/~suri/Detecting%20Buffer%20Over.pdf), a translation of LLVM to a simple non-deterministic language to detect buffer overflows. It involves (1) printing a control flow graph of basic blocks of a function (easily done) (2) translating each llvm statement to a corresponding data flow language (needs ASTs to

Hi, I've developed editor prototype for TableGen files (td). It is Eclipse plugin based on IMP project (The IDE Meta-Tooling Platform). Editor has outline, folding, coloring, go to definition, etc. As any prototype, editor has some limitations (e.g. no cross-file indexing). If there is any interest to such tool I will improve it a bit and then publish. Also considering llvm asm (ll) editing

Hi again, My point is that your code could not be written in C++ at this time because the only complete compiler for C++ is LLVM-GCC. It will do little endian optimizations on your x86 box and make the resultant bitcode file not work on the ARM processor. It is possible to write an endian-agnostic bitcode file but I don't think all modern LLVM compilers support it. Also the FAQ also

Samuel Crow <samuraileumas at yahoo.com> writes: > I have attached the logfiles here. I think you didn't set CMAKE_BUILD_TYPE while configuring the cmake build. On your build directory, please do: make clean cmake -DCMAKE_BUILD_TYPE=Debug path/to/your/llvm/source/root make If that doesn't work, show the exact command lines you used for invoking cmake and the

I build llvm+clang almost every day with Ubuntu 10.04. Everything goes fine. I guess it's your VirtualBox has too little memory. On Thu, May 6, 2010 at 4:12 AM, Samuel Crow <samuraileumas at yahoo.com> wrote: > After waiting through about 2 hours of hard drive spinning for Clang to > link under my Xubuntu Lucid Lynx Linux setup on VirtualBox, ld finally just > gave up trying

Samuel Crow <samuraileumas at yahoo.com> writes: > The single-threaded build failed the same place as the double threaded build > failed which is the same place I just indicated in my previous post. The > ../llvm/configure script version failed with OCaml building with about 600 > assembler errors since I built it in AMD64 mode. (Oops.) Should I disable > OCaml from

Samuel Crow <samuraileumas at yahoo.com> writes: > Here's some of what it would take to make portable bitcodes in C or LLVM Assembly: A look at the work done on ANDF in the 90's may be helpful. I've only skimmed it but there's been some deep thinking about stuff like this. -Dave

Forgot to CC the list, sorry. ----- Forwarded Message ----- > From: Samuel Crow <samuraileumas at yahoo.com> > To: FlyLanguage <flylanguage at gmail.com> > Cc: > Sent: Monday, July 18, 2011 10:40 AM > Subject: Re: [LLVMdev] RTTI gone in 3.0? > > Hi FlyLanguage, > > I thought LLVM disabled RTTI a long time ago.  It was just too slow. > > --Sam >

----- Original Message ---- > From: Óscar Fuentes <ofv at wanadoo.es> > To: Samuel Crow <samuraileumas at yahoo.com> > Cc: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> > Sent: Wed, January 5, 2011 5:00:00 PM > Subject: Re: Build problems and workarounds with CMake and XCode > > Samuel Crow <samuraileumas at yahoo.com> writes: > >