similar to: [LLVMdev] large linking time

Hi LLVMdev, The stuff I am working on requires linking 9-10 LLVM libraries, along with a few libs of my own. The linker is taking a long time to do that, about 6 mins (on a P4 with 512 MB mem). I tried the latest (2.14) release of binutils, but that didn't help. Is anyone aware of any solution to this? Thanks, Rahul

MetaSplit is an anlysis I just finished writing. It doesn't alter anything, all it does is build a set of "program instructions". For some reason even though if I run it with any other combination of passes I've found, anytime I run it with mem2reg I get a seg fault in dyn_cast! Here's output: Starting program: /mounts/zion/disks/0/localhome/pmeredit/llvm/tools/Debug/opt

Attached is the patch I've been building arm-eabi with, which might help with linux-gnueabi. I disable multilib to get around several bugs with thumb. I build cross binutils first, then llvm, then llvm-gcc with newlib merged in. The following bugs need to be addressed for these non-Darwin ARM targets: 1388 2313 2545 2985 deep On Fri, Mar 13, 2009 at 12:30 AM, Misha Brukman <brukman at

On Wed, 23 Jun 2004, Patrick Meredith wrote: > Somehow it fails with operand out of bounds when the number of operands > is 2 and I am asking for the second operand. Second meaning operand 1. Okay, so you have something like this: if (CallInst *CI = dyn_cast<CallInst>(...)) { ... = CI->getOperand(1); } Can you send in this snippet of code, the assertion, and the

I thought this conversation was worth saving. DannyB who did wonderful things with GCC's use of bugzilla has offered the same capability to LLVM. Thanks, Danny! <DannyB> sabre: BTW, if you need any of the bugzilla fun i have implemented for gcc, let me know [22:47] <sabre> Cool, what kinds of things do you have? [22:47] <DannyB> Besides the triplet stuff, i changed some of

Hi, I am wondering whether the bytecode generated by my llvm-gcc is correct? When I run $ llvm-gcc hello.c -o hello What I get is hello.exe.bc, and hello.exe (I can actually llvm-dis the bytecode file which is hello.exe.bc). However, I do not get a shell script(named hello) as stated in the documentation... Best Regards, Kiat On 5/25/05, Aaron Gray <angray at beeb.net> wrote: >

On Mar 11, 2009, at 9:44 PM, Misha Brukman wrote: > The problem I've had is building an LLVM cross-compiler from Linux/ > x86 to Linux/ARM (as has another llvm-dev poster). Someone > mentioned to me off-list that he managed to get it to build, but I > haven't been able to reproduce the build using his instructions > (I'll post my results in another thread).

Hi LLVM'ers, Here is my second try to document, how to build the llvm system for MinGW on Windows. Henrik. ============================================================= Henrik Bach LLVM Open Source Developer e-mail: henrik_bach_llvm at hotmail.com ============================================================= 'Nothing is impossible; The impossible just takes longer time :)' -

On Thu, Mar 12, 2009 at 6:17 AM, Dietmar Ebner <ebner at complang.tuwien.ac.at>wrote: > On Mar 11, 2009, at 9:44 PM, Misha Brukman wrote: > > The problem I've had is building an LLVM cross-compiler from Linux/ > > x86 to Linux/ARM (as has another llvm-dev poster). Someone > > mentioned to me off-list that he managed to get it to build, but I > > haven't

Can someone with llvm-gcc/ARM expertise (Dale?) please review Sandeep's patch? The patch works for me in building an LLVM-based cross-compiler from x86_64/Linux to ARM/Linux. I have been able to build without the patch to the asm file, but several people have reported needing the asm patch on http://llvm.org/PR2545 . On Thu, Mar 12, 2009 at 8:39 PM, Sandeep Patel <deeppatel1987 at

void MetaSplit::handleProgramUses(Value *V){ if(!isa<BasicBlock>(V)) programValues.insert(V); if(User *U = dyn_cast<User>(V)){ User::op_iterator OB = U->op_begin(), OE = U->op_end(); for(; OB != OE; ++OB){ if(CallInst *CI = dyn_cast<CallInst>(*OB)){ Function *F = CI->getCalledFunction(); if(F == ii || F == fi || F == vi || F == di || F == ci

Dear All, I would like to create the release branch for the llvm-gcc source code tomorrow morning. I imagine this will be okay as llvm-gcc seems pretty healthy and no one is currently doing any development on it. If there's something that needs to be fixed, or you're working on llvm-gcc, please email the list so that I can delay creating the branch as appropriate. I won't be

I've committed my scripts that simplify building Linux/x86 -> Linux/ARM crosstool. There are 2 parts to using this: * llvm/utils/crosstool/create-snapshots.sh creates tarballs for LLVM and LLVM-GCC from HEAD SVN or a specific revision of your choice * llvm/utils/crosstool/ARM/build-install-linux.sh builds and installs a Linux/x86 -> Linux/ARM crosstool using the snapshots generated

> I would like to create the release branch for the llvm-gcc source code > tomorrow morning. I imagine this will be okay as llvm-gcc seems pretty > healthy and no one is currently doing any development on it. > > If there's something that needs to be fixed, or you're working on > llvm-gcc, please email the list so that I can delay creating the branch as >

On Thu, Mar 12, 2009 at 8:39 PM, Sandeep Patel <deeppatel1987 at gmail.com>wrote: > Attached is the patch I've been building arm-eabi with, which might > help with linux-gnueabi. I disable multilib to get around several bugs > with thumb. I build cross binutils first, then llvm, then llvm-gcc > with newlib merged in. > > The following bugs need to be addressed for

I am using the below configuration: ./configure --with-llvmgccdir=/home/jcmartin78/LLVM/llvm-gcc4.2 --prefix=/home/jcmartin78/local --enable-optimized=1 --enable-debug-runtime --enable-jit --enable-targets=arm --target=arm When I use LLVMC to compile a simple program I get this: $ llvmc hello.c llc: error auto-selecting target for module 'No available targets are compatible with this

LLVM, When we recompile, is it possible to "make" only one of the tools, or at least relink only the tools whose object files have changed? Thanks Dave

Howdy, folks! I am trying to update this page with relevant info: http://llvm.cs.uiuc.edu/docs/GettingStarted.html#hardware I know there are several of using LLVM on Windows (native or on top of Cygwin), so if you can supply me with your disk-space usage for the LLVM tree, debug build, and llvm-gcc frontend install, I would appreciate it. Please reply off the list, as this isn't of

I have not used llvmc to build ARM binaries, but llvm-gcc does work.There's a script to build llvm-gcc x86 -> ARM cross-compiler in llvm/utils/crosstool/ARM/ . 2009/6/29 Juan Carlos Martinez Santos <juanc.martinez.santos at gmail.com> > I am using the below configuration: > > ./configure --with-llvmgccdir=/home/jcmartin78/LLVM/llvm-gcc4.2 >

On 4/19/06, Rogelio Serrano <rogelio.serrano at gmail.com> wrote: > On 4/16/06, Tanya Lattner <tonic at nondot.org> wrote: > > > > I've put the pre-release tar balls here: > > http://llvm.org/prereleases/1.7/ > > > > The build failed on i686-pc-linux-gnu. > > llvm[2]: Flexing FileLexer.l > llvm[2]: Compiling FileLexer.cpp for Release build