search for: jakaboski

Hi Robert- I notice that llvm-lua requires LLVM 2.4 rather than anything recent - are there any plans to upgrade? Alastair On 8 Jun 2009, at 14:34, Robert G. Jakabosky wrote: > > Have you tried llvm-lua? It adds JIT & static compiling support to > the Lua VM > using LLVM as the backend. I just released version 1.0 about a week > ago. > > The project website is

Have you tried llvm-lua? It adds JIT & static compiling support to the Lua VM using LLVM as the backend. I just released version 1.0 about a week ago. The project website is here: http://code.google.com/p/llvm-lua/ On Friday 05, Marcus Zetterquist wrote: > Hi! > > > Today we use Lua to let 3rd party developers add driver-like modules > to our application. > > The

Hi! Today we use Lua to let 3rd party developers add driver-like modules to our application. The advantages to using Lua compared to DLL:s etc. are that: 1) the same driver binary can be used on all OS:es and processor architectures etc. 2) We can provide a small API to the Lua drivers and they _cannot_ call any other external functions. 3) A buggy driver cannot crash our application.

I would like to announce the availability of llvm-lua. llvm-lua, converts Lua bytecode to LLVM IR code and supports JIT and static compiling. Using LLVM gives Lua JIT support on cpu architectures other then x86. I converted the Lua bytecode dispatch loop code into a set of C functions one for each opcode. The opcode functions take two parmeters one is the current Lua function's state,

If your project works with LLVM 2.7 and you want it included in the release notes, please email me a blurb to include ASAP. -Chris

I'm working on a bug where LLVM takes over six minutes to compile a module. After some hand-editing, the module looks like this: class half { private: union uif { unsigned int i; float f; }; static const uif _toFloat[1 << 16]; }; const half::uif half::_toFloat[1 << 16] = { {0x00000000}, {0x33800000}, {0x34000000}, {0x34400000}, {0x34800000},

>> Dear All, I have been trying for days but still cannot break this barrier. May I get your help? I have compiled llvm-2.1 successfully and make install. When I proceed with llvm-gcc-4.2-2.1, however, I keep getting linking error as attached. Some functions with totally different content conflict with each other in linking process. That is a Linux box (Debian, with 2.6.23-1