similar to: [LLVMdev] cross-compiling with llvm

> 1. Is it possible at all to cross-compile with llvm? Yes, this is possible. I've cross-compiled from x86 to MIPS using LLVM. However, the codes I compiled using this technique did not always run correctly. You may have better luck with PPC. > 2. I allready have a gcc cross-compiler for power-pc, do i need > this or > does llvm contain its own? How can i tell llvm to

I just updated from CVS, and after doing a clean rebuild I get this error: /Users/bocchino/llvm-checkin/src/include/llvm/IntrinsicInst.h: In static member function 'static bool llvm::DbgInfoIntrinsic::classof (const llvm::IntrinsicInst*)': /Users/bocchino/llvm-checkin/src/include/llvm/IntrinsicInst.h:77: error: 'dbg_declare' is not a member of 'llvm::Intrinsic'

I've done several CVS head builds today .. no problems on Linux. Reid. On Fri, 2006-04-07 at 11:53 -0500, Chris Lattner wrote: > On Fri, 7 Apr 2006, Robert L. Bocchino Jr. wrote: > > > I did a utils/cvsupdate, and there are no conflicts. srcdir != objdir. This > > is on persephone. > > > > Are you not getting this error? Perhaps I should check out a fresh

On Fri, 7 Apr 2006, Robert L. Bocchino Jr. wrote: > I just updated from CVS, and after doing a clean rebuild I get this error: Are you sure that no conflicts prevented updating from going smoothly? How are you building (srcdir ==/!= objdir)? -Chris > /Users/bocchino/llvm-checkin/src/include/llvm/IntrinsicInst.h: In static > member function 'static bool

I did a utils/cvsupdate, and there are no conflicts. srcdir != objdir. This is on persephone. Are you not getting this error? Perhaps I should check out a fresh tree and try to compile it? Rob On Apr 7, 2006, at 11:40 AM, Chris Lattner wrote: > On Fri, 7 Apr 2006, Robert L. Bocchino Jr. wrote: >> I just updated from CVS, and after doing a clean rebuild I get >> this

I'm guessing the problem occurred because I hadn't updated in a while (maybe a couple of weeks?) and I had an old Intrinsics.gen file hanging around in my source directory that was getting picked up by the makefile for some reason. This is a bug, but maybe it's harmless because there's a onetime workaround (delete the file by hand) and it won't be a problem for

When I tried this a while back, the .so file wasn't being built on Mac OS X. Now it looks like it is. I got dynamic loading to work following the instructions in http://llvm.cs.uiuc.edu/docs/ WritingAnLLVMPass.html. However, there was a typo in the instructions (it should say LOADABLE_MODULE = 1), and I fixed that and committed it. I also fixed the sample/lib/sample Makefile to

On Fri, 7 Apr 2006, Robert L. Bocchino Jr. wrote: > I did a utils/cvsupdate, and there are no conflicts. srcdir != objdir. This > is on persephone. > > Are you not getting this error? Perhaps I should check out a fresh tree and > try to compile it? Nope, I don't think anyone else is getting this error. If you could try a fresh build that would be great, I'll fire

Hi, In the past, I haven't been able to get dynamically loaded passes to work under OS X. When I follow the instructions in the LLVM documentation, everything works fine for Linux, but OS X has a different way of handling dynamic loading, and the files that the dynamic loader is trained to look for don't exist. In the past, I've worked around this by just linking all my

Here's why I was questioning the change to sample/lib/sample Makefile: make[4]: Entering directory `/proj/llvm/build/projects/sample/lib/sample' llvm[4]: Compiling sample.c for Debug build (PIC) llvm[4]: Linking Debug Shared Library sample.so llvm[4]: Linking Debug Object Library sample.o /proj/install/lib/libstdc++.a: member /proj/install/lib/libstdc++.a (allocator-inst.o) in archive is

I'll test on Darwin/PPC, precompiled llvmgcc, objdir == srcdir. Rob On Apr 16, 2006, at 1:42 PM, Chris Lattner wrote: > On Sun, 16 Apr 2006, Tanya Lattner wrote: >> For testing, we would like a mix of people to do x86 and ppc. >> Please send email to the list if you plan to test, what >> architecture, and if you will use the llvm-gcc binary or compile >> it

The answer lies in the lib/System/ltdl.c which is the dynamic loader used by LLVM for cross platform dynamic loading. If there are paths or files that we're not looking for on OS/X then that needs to be fixed. Could you be a little more specific about what failures you are experiencing? Reid. On Fri, 2006-01-06 at 14:25 -0600, Robert L. Bocchino Jr. wrote: > Hi, > > > In the

OK, when I copy $(SRCDIR)/include/llvm/Intrinsics.gen to $(OBJDIR)/ include/llvm/ by hand after building (and failing) once, the build succeeds. This is definitely a makefile bug. Rob On Apr 7, 2006, at 11:40 AM, Chris Lattner wrote: > On Fri, 7 Apr 2006, Robert L. Bocchino Jr. wrote: >> I just updated from CVS, and after doing a clean rebuild I get >> this error: > >

Apple are to move over to Intel CPU's :- http://www.apple.com/pr/library/2005/jun/06intel.html http://news.bbc.co.uk/2/hi/technology/4612951.stm Big shame, narrowing of the market, and probably the end of the PowerPC. Aaron -------------- next part -------------- An HTML attachment was scrubbed... URL:

I haven't seen anyone claim x86 linux objdir == srcdir, so I'll test it out. Missed the 18th,but I'll try to have it done asap. On Apr 18, 2006, at 2:51 PM, Robert L. Bocchino Jr. wrote: > I'll test on Darwin/PPC, precompiled llvmgcc, objdir == srcdir. > > Rob > > On Apr 16, 2006, at 1:42 PM, Chris Lattner wrote: > >> On Sun, 16 Apr 2006, Tanya Lattner

Hi, I just updated from source and got this at the top of the master Makefile: LEVEL = . DIRS = lib/System lib/Support utils lib ifeq ($(MAKECMDGOALS),tools-only) DIRS += tools else ifneq ($(MAKECMDGOALS),libs-only) DIRS += runtime docs OPTIONAL_DIRS = examples projects endif endif This causes my build to be incorrect. In the general case, it doesn't build the tools, and

I wouldn't count the PowerPC out entirely, as it will continue to be used in game platforms (and maybe other embedded platforms?). But yes, in the desktop hardware market, it seems there's now only one game in town. Rob On Jun 12, 2005, at 11:16 AM, Aaron Gray wrote: > Apple are to move over to Intel CPU's :- >   >        

Hi all LLVMdev! Here is a question: I try to understand how I can realize a debugging in LLVM!? I have written a back end for my target and now I need a debug. I asked developers Chris Lattner and Robert L. Bocchino. They recommend me ask the LLVMdev. Is there a tool like "llvm-db" about Robert said? Here a mail from Robert: On Jun 29, 2009, at 17:14 PM, Robert L. Bocchino

Hi Terry, Reid is exactly right about the benefits of static (link-time) optimization for whole programs. When all libraries are available, it could alllow significantly better optimization without run-time overhead. But it is increasingly common today for libraries to be dynamically linked. In these cases, you could get the benefits of LLVM optimization in two ways, *if* you compile the

Hi, Inserting a call instruction is a bit of a pain. The only way I know how to do it is to write a bunch of code like the following: std::vector<const Type*> formalArgs; formalArgs.push_back(arg1->getType()); formalArgs.push_back(arg2->getType()); ... formalArgs.push_back(argn->getType()); std::vector<Value*> args; args.push_back(arg1);