search for: llvmsrcdir

...h. The > configure script should detect that you have llvm-gcc4 and disable > building these libraries (which are only needed by llvm-gcc3). The problem was that I had forgot to use --enable-llvm when compiling GCC :-( One small improvement that I noticed because of my mistake is to declare LLVMSRCDIR in gcc/Makefile.in using := instead of = This will cause make to run grep and sed only once. I found this because there was a grep error message for each compiled file :-) Thank you very much, Rafael

...t; > -Dave > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev AFAIK, LiveVariables analysis pass (from $LLVMSRCDIR/lib/CodeGen/LiveVariables.cpp) is used and improved by LiveIntervals analysis (lies in the same directory). LiveIntervals analysis handles the false interference case (you've shown above). You can read about the idea from the paper by Alkis Evlogimenos: http://llvm.org/ProjectsWithLLVM/2004-Fal...

Toward a better register allocator, I'm attempting to understand the dataflow information available to the allocator. What's the difference between LiveInterval information and LiveVariable information? If a LiveInterval is based on a linear ordering of the machine instructions, isn't it rather conservative in nature? Let's say I have a typical diamond CFG: A

On Thu, 20 Apr 2006, [UTF-8] Rafael Esp?ndola wrote: > I am trying to bootstrap the just released gcc 4.0.1 and the cvs head llvm. > > I was able to build the llvm tools without a problem. > gcc has a small problem (from the apple branch IIRC): libojc is built > unconditionally, so objc must be in the --enable-languages option for > the build to be successful. > > Building

I am trying to bootstrap the just released gcc 4.0.1 and the cvs head llvm. I was able to build the llvm tools without a problem. gcc has a small problem (from the apple branch IIRC): libojc is built unconditionally, so objc must be in the --enable-languages option for the build to be successful. Building the rest of llvm fails with llvm[3]: Compiling crtend.ll to crtend.bc for Debug build

...lhigu/stow_sources/llvm-svn/include > > and from install directory. > > elhigu at mr-lenovo:~/stow_sources/llvm-svn$ ~/stow_installs/bin/llvm- > config --includedir > /home/elhigu/stow_installs/include > >> It sounds like the real problem is that LLVMOBJDIR and >> LLVMSRCDIR are pointing to the wrong places. What did you pass to >> --enable-llvm when you configured llvm-gcc? > > When I compile llvm-gcc with llvm installation without llvm sources > I pass 'llvm-config --prefix' for --enable-llvm when I build llvm- > gcc towards llvm source...

...-Dave >> >> _______________________________________________ >> LLVM Developers mailing list >> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu >> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev > > > AFAIK, LiveVariables analysis pass > (from $LLVMSRCDIR/lib/CodeGen/LiveVariables.cpp) is used and improved by > LiveIntervals analysis (lies in the same directory). > LiveIntervals analysis handles the false interference case (you've shown > above). You can read about the idea from the paper by Alkis Evlogimenos: > http://llvm.org/Proje...