search for: gorin

...on linux ubuntu 9.04 in x86_64 mode. Lli is generated from the current version of the svn repository. The backtrace and full bt from gdb are enclosed with this message. Is there a solution to this issue or is it due to the fact that lli can't support dwarf informations yet? Many thanks Jerôme GORIN -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20091028/a78875fd/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: bt Type: application/octet-stream Size:...

...We have already tested this issue with lli in its 2.9 version, and this bug still stays the same. LLVM 2.9, including lli, has been compiled on the board with Ubuntu 10.10; ARM and thumbs instructions are enabled. Has anybody else done the LLVM experiment on the pandaboard? Kind regards, Jérôme Gorin -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20110615/1f3ac58a/attachment.html>

...roid nk r4 from crystax that supports c++ and rtti libs. I'm facing the problem that there gcc compiler doesn't support __clear_cache function of Memory.cpp (line 699) for the librarie LLVMSystem. Is there a way to bypass this limitation without puts a comment on this line? Regards Jérôme Gorin -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20101118/6d9289a0/attachment.html>

Thank very much for this answer, so my last question will be: is it possible to use the LLVM JIT on a PS3 with Yellow Dog 6.2 distribution, instead of the LLVM interpreter, by using the PPE as it seems to be similar to 64-bit PowerPC processors? 2009/12/18 Scott Michel <scooter.phd at gmail.com> > Jerome: > > No, there are no plans to JIT to SPU. That's considerably more

Jerome: No, there are no plans to JIT to SPU. That's considerably more complicated -- you'd have to figure out when to JIT to the SPU and live with all of the constraints that the SPU imposes (data reformatting, r/w DMA, ensure your code lives in 256K unless you can manage to interface with the virtual I-cache work.) Basically, it's not trivial and it doesn't quite fit into the

Hi, I've successfully compiled and cross-compiled llvm 2.6 libraries for many OS and platforms (x86, cell, ppc and arm), but I still have a problem to cross-compile the llvm libraries from Mac 10.5.6 (X86) to iPhone device 3.1.2. I've tryed many ways (CMake, autoconf, XCode 3.2) but i still have a problem for the LLVMXXXCodeGen.a generation, due to a script problem with

Hi, I've successfully compiled and cross-compiled llvm 2.6 libraries for many OS and platforms (x86, cell, ppc and arm), but I still have a problem to cross-compile the llvm libraries from Mac 10.5.6 (X86) to iPhone device 3.1.2. I've tryed many ways (CMake, autoconf, XCode 3.2) but i still have a problem for the LLVMXXXCodeGen.a generation, due to a script problem with intrisics.gen.

Hi, I'm yet working on the LLVM ExecutionEngine portability (2.6 release version) and I get two different problems depending on the platform. The first problem concerns compilation on MacOs X (10.5.5) with an X86 processor, when trying to compile my own project containing the ExecutionEngine class and the linker class. I get links problem with "_ffi_type_sint16",