search for: shadowlab

Hi Jean-Daniel On Mon, Oct 19, 2009 at 3:24 PM, Jean-Daniel Dupas <devlists at shadowlab.org>wrote: > > Le 19 oct. 2009 à 15:05, Kenneth Uildriks a écrit : > FWIW, there is a LLVM bar camp planed in Paris the next month: > > http://barcamp.org/LLVM%20BarCamp%20Paris (French web page) > > > -- Jean-Daniel > Could you please tell me if it will be in French...

Le 20 oct. 2009 à 10:27, Artur Pietrek a écrit : > Hi Jean-Daniel > > On Mon, Oct 19, 2009 at 3:24 PM, Jean-Daniel Dupas <devlists at shadowlab.org > > wrote: > > Le 19 oct. 2009 à 15:05, Kenneth Uildriks a écrit : > FWIW, there is a LLVM bar camp planed in Paris the next month: > > http://barcamp.org/LLVM%20BarCamp%20Paris (French web page) > > > -- Jean-Daniel > > Could you please tell me if it will b...

...ght need to write my own utility to do this parsing/registering.. But it'd be nice to at least be able to see some code from the runtime that does this job, so I can understand what's going on, but I can't find anything like that! On 7 May 2012 22:17, Jean-Daniel Dupas <devlists at shadowlab.org> wrote: > > > Le 7 mai 2012 à 17:07, Jules a écrit : > > > Hello, I've been trying to get some OSX code to execute within the JIT, > > and it's been causing me some major headaches! > > > > I'm attempting to JIT-compile some code which uses ext...

On Thu, May 23, 2013 at 6:01 AM, Jean-Daniel Dupas <devlists at shadowlab.org>wrote: > If you want to build a clang version that target x86 and ARM on an x86 > machine and your actual compiler does not support compiling for ARM, you > have to use the just built clang. > Using the just-built-clang will only work if compiler-rt has access to each target...

...utility to do this parsing/registering.. But it'd be nice to at least > be able to see some code from the runtime that does this job, so I can > understand what's going on, but I can't find anything like that! > > > On 7 May 2012 22:17, Jean-Daniel Dupas <devlists at shadowlab.org> wrote: >> >> >> Le 7 mai 2012 à 17:07, Jules a écrit : >> >>> Hello, I've been trying to get some OSX code to execute within the JIT, >>> and it's been causing me some major headaches! >>> >>> I'm attempting to JIT-...

Hi, So for everybody who could be interested in LLVM Camp in Paris - it will be in French. I've just received an email from Eric Mahé. Artur On Tue, Oct 20, 2009 at 10:36 AM, Jean-Daniel Dupas <devlists at shadowlab.org>wrote: > > Le 20 oct. 2009 à 10:27, Artur Pietrek a écrit : > > Hi Jean-Daniel >> >> On Mon, Oct 19, 2009 at 3:24 PM, Jean-Daniel Dupas < >> devlists at shadowlab.org> wrote: >> >> Le 19 oct. 2009 à 15:05, Kenneth Uildriks a écrit : >>...

Jean-Daniel Dupas <devlists at shadowlab.org> writes: > Le 29 janv. 2011 à 09:33, Mark Lacey a écrit : > >> I know this comes up periodically, but it looks like it has been a few months since there was any posting indicating that having an official git mirror for LLVM, et al. was still in the works. >> >> I am...

Hello, Is it possible to use LLVM like JVM (virtual machine)? If so, How? Can this be used to create hardware-independent and OS-independent binaries? Thank you

Whoops, missed the list. ----- Forwarded Message ----- > From: Samuel Crow <samuraileumas at yahoo.com> > To: Jean-Daniel Dupas <devlists at shadowlab.org> > Cc: > Sent: Wednesday, April 18, 2012 10:24 AM > Subject: Re: [LLVMdev] Hi guys and llvmbrains! :P > > > > >> ________________________________ >> From: Jean-Daniel Dupas <devlists at shadowlab.org> >> To: toredhiddenuser at tormail.net &...

Jean-Daniel Dupas <devlists at shadowlab.org> writes: >> P.S. Weren't we planning on removing the Make-based build system in >> the next few months a year ago? > > It always lacks some important features, like building compiler-rt > with just-built clang: http://llvm.org/bugs/show_bug.cgi?id=14109 The configu...

Hello, While working on lld code, I encountered a couple of memory management issues. If lld should be usable as a library, I assume it should not leaks any memory when performing a single link pass (UniversalDriver::link(arc, argv)). Actually, after calling that function, I got some major leaks. I may be wrong, but I think there is 3 major leaks. - One of the main leak is in FileArchive. When

On Mon, Apr 29, 2013 at 3:11 PM, Jean-Daniel Dupas <devlists at shadowlab.org> wrote: > Just out of curiosity, what would be the main benefit of this approach vs DKMS which is already widely used ? > Thanks Dupas. I checked DKMS you mentioned, basically DKMS is just a ko and its sources management tool. It's not easy to deploy ko source into target machine...

Hi Jean-Daniel, My fault, I'm sure, but I don't see the problem yet. Is it possible your version of llvm/Config/AsmPrinters.def has X86 listed twice? - Daniel On Mon, Aug 2, 2010 at 12:43 AM, Jean-Daniel Dupas <devlists at shadowlab.org> wrote: > Hello, > > After I try making a clean build and got the following error: > > llvm[3]: Compiling EDDisassembler.cpp for Release build > In file included from /llvm/include/llvm/Target/TargetSelect.h:38, >                 from /llvm/lib/MC/MCDisassembler/EDDisass...

...ss, only to take a look (like a brush). I think it's going to be necessary to define a standard format for each kind of information (for example, which information for an optimization pass: the analysis it uses in the "see also" section?). 2009/3/23 Jean-Daniel Dupas <devlists at shadowlab.org> > > http://wiki.llvm.org/ ? > > > Le 23 mars 09 à 19:04, Bill Wendling a écrit : > > > So, um...what's the URL for this wiki? > > > > -bw > > > > On Mar 23, 2009, at 10:29 AM, Daniel Berlin wrote: > > > >> Installed it, tha...

On Mon, Apr 29, 2013 at 08:14:57PM +0800, Jovi Zhang wrote: > On Mon, Apr 29, 2013 at 3:11 PM, Jean-Daniel Dupas > <devlists at shadowlab.org> wrote: > > Just out of curiosity, what would be the main benefit of this approach vs DKMS which is already widely used ? > > > Thanks Dupas. > > I checked DKMS you mentioned, basically DKMS is just a ko and its > sources management tool. > > It's not easy...

Hello, After I try making a clean build and got the following error: llvm[3]: Compiling EDDisassembler.cpp for Release build In file included from /llvm/include/llvm/Target/TargetSelect.h:38, from /llvm/lib/MC/MCDisassembler/EDDisassembler.cpp:37: /llvm/stage1/include/llvm/Config/AsmPrinters.def: In function ‘void LLVMInitializeX86TargetAsmPrinter()’:

On May 23, 2013, at 10:30 AM, Greg Fitzgerald <garious at gmail.com> wrote: > > On Thu, May 23, 2013 at 6:01 AM, Jean-Daniel Dupas <devlists at shadowlab.org> wrote: > If you want to build a clang version that target x86 and ARM on an x86 machine and your actual compiler does not support compiling for ARM, you have to use the just built clang. > > Using the just-built-clang will only work if compiler-rt has access to each target's s...

AFAIK, ld does not use DYLD_LIBRARY_PATH to lookup libLTO.dylib but contains a reference to @executable_path/../lib/libLTO.dylib. The only way I managed to load a different LTO library than the default one is to create a symlink pointing to the actual ld binary (as returned by 'xcrun -find ld') and making sure the library I want to load is placed at ../lib/libLTO.dylib relatively to this

For dogfooding the compiler I normally use is a LTO bootstrap of clang. On linux that is simple to do that since clang passes the correct plugin to the linker. On OS X ld64 uses libLTO.so it finds via DYLD_LIBRARY_PATH. Should clang set that before running the linker? Is there a better way for clang to tell the linker which libLTO.so to use? Cheers, Rafael

Hi Speaking about a good existing build system in python, there is waf : http://code.google.com/p/waf/ It is in my opinion far more better than cmake on any point (performance, flexibility, easy to use, ...) ... 2012/6/21 Jean-Daniel Dupas <devlists at shadowlab.org> > > Le 21 juin 2012 à 11:34, Manuel Klimek a écrit : > > On Thu, Jun 21, 2012 at 10:43 AM, Charles Davis <cdavis at mymail.mines.edu>wrote: > >> >> On Jun 20, 2012, at 6:19 PM, Chandler Carruth wrote: >> >> On Wed, Jun 20, 2012 at 5:13 PM, Nick...