search for: llvmobjdir

If llvm is build with srcdir != objdir, building gcc will fail with ../../llvm-gcc4-1.7.source/gcc/llvm-internal.h:36:36: error: llvm/Support/DataTypes.h: No such file or directory This happens because DataTypes.h is a generated header. Adding -I$(LLVMOBJDIR)/include to INCLUDES in Makefile.in:878 solves the problem. One more thing, is the modified GCC available in some svn or cvs repository? Thanks, Rafael

In http://llvm.org/svn/llvm-project/llvm-gcc-4-2/trunk/README.LLVM I can read "Below we assume the LLVM OBJDIR is $LLVMOBJDIR". But in http://llvm.org/docs/GettingStarted.html#terminology I read about OBJ_ROOT. Is this the same? Then terminology is inconsistent. But actually I don't think so, because the text says "These are not environment variables". Still it's confusing, because I was asked...

...source, but got the following error when compiling: > > > > configure: error: You must specify valid path to your LLVM tree with > > --enable-llvm=DIR > > make: *** [configure-gcc] Error 1 > > > > I've done the following in csh before hand: > > $ setenv LLVMOBJDIR /home/napi/proj/c2jvm/llvm/llvm-gcc/obj > > > > Where did I go wrong? > > LLVMOBJDIR needs to be the LLVM tree, not llvm-gcc. Could you give me an example of the LLVM tree and of the setting of LLVMOBJDIR? Thanks. Napi

...ollowed the README.LLVM file that comes with LLVM-GCC 4.0 Front End source, but got the following error when compiling: configure: error: You must specify valid path to your LLVM tree with --enable-llvm=DIR make: *** [configure-gcc] Error 1 I've done the following in csh before hand: $ setenv LLVMOBJDIR /home/napi/proj/c2jvm/llvm/llvm-gcc/obj Where did I go wrong? Thanks. Napi On Fri, 2007-05-11 at 23:38 -0700, Chris Lattner wrote: > On Fri, 11 May 2007, me22 wrote: > > I'm not exactly sure how llvm-g++ works. I think it goes through the > > standard gcc sequence (gimple, r...

...x86_64 GNU/Linux my gcc version is 4.2.1 2. I've unpacked llvm-gcc-4.2-2.6.source.tar.gz under the llvm-gcc directory. I've also created two subdirectories called "install" and "obj" under the same llvm-gcc. 3. Then I did the following, based on README.LLVM : %setenv LLVMOBJDIR /home/eliseuf/llvm/llvm-gcc/obj %cd obj %../llvm-gcc4.2-2.6.source/configure --prefix=`pwd`/../install --program-prefix=llvm- --enable-llvm=$LLVMOBJDIR --enable-languages=c --disable-multilib %gmake 4. Result: gmake aborts with the message: configure: error: You must specify valid path to your LL...

Dear Anton, you can add your register allocator strait iin the "lib/CodeGen/Passes.cpp", and then 're-make' it: "makellvm llc", on the top of lib/CodeGen. It is faster than running make from LLVMOBJDIR. The problem is that it only add to llc the changes on the lib/CodeGen directory. If you change other parts, a make from LLVMOBJDIR will synchronize it. Try adding code like this to your Passes.cpp file: //===---------------------------------------------------------------------===// /// /// RegAl...

...s with LLVM-GCC 4.0 > Front End source, but got the following error when compiling: > > configure: error: You must specify valid path to your LLVM tree with > --enable-llvm=DIR > make: *** [configure-gcc] Error 1 > > I've done the following in csh before hand: > $ setenv LLVMOBJDIR /home/napi/proj/c2jvm/llvm/llvm-gcc/obj > > Where did I go wrong? LLVMOBJDIR needs to be the LLVM tree, not llvm-gcc. -Tanya > > Thanks. > > Napi > > On Fri, 2007-05-11 at 23:38 -0700, Chris Lattner wrote: >> On Fri, 11 May 2007, me22 wrote: >>> I'm not...

Hi! I've did what Jim Laskey wrote but llc didn't reckognize my regalloc option. So I moved my allocator implementation into seperate folder within CodeGen and wrote separate makefile for it (like in "Writing an LLVM pass" tutorial). But when I run "make" from LLVMOBJDIR it doesn't enter the RegAlloc directory and when linking llc an error like "createGraphColoringRegAlloc not defined" occurs. What am I doing wrong? :) On 8/3/06, Chris Lattner <sabre at nondot.org> wrote: > On Thu, 3 Aug 2006, Jim Laskey wrote: > > To force the load/...

On Thu, 3 Aug 2006, Jim Laskey wrote: > To force the load/linking of your register allocator into the llc/lli tools, > add your create function's global declaration to "Passes.h" and add a > "pseudo" call line to "llvm/Codegen/LinkAllCodegenComponents.h" . Another note: with this new functionality you should be able to dynamically load register

...Eliseu, > 2. I've unpacked llvm-gcc-4.2-2.6.source.tar.gz under the llvm-gcc > directory. I've also created two subdirectories > called "install" and "obj" under the same llvm-gcc. > > 3. Then I did the following, based on README.LLVM : > > %setenv LLVMOBJDIR /home/eliseuf/llvm/llvm-gcc/obj first you need to build llvm itself. LLVMOBJDIR points to where you built llvm, not where you are planning to build llvm-gcc. Ciao, Duncan.

On Fri, 11 May 2007, me22 wrote: > I'm not exactly sure how llvm-g++ works. I think it goes through the > standard gcc sequence (gimple, rtl, and such) but then outputs LLVM > (http://llvm.org/docs/LangRef.html), which is the intermediate > representation used by the rest of the chain. To make an LLVM backend > you would not need to deal with RTL and such at all. llvm-g++

...ira <fernando at cs.ucla.edu> wrote: > > > Dear Anton, > > you can add your register allocator strait iin the > "lib/CodeGen/Passes.cpp", and then 're-make' it: "makellvm llc", on the > top of lib/CodeGen. It is faster than running make from LLVMOBJDIR. The > problem is that it only add to llc the changes on the lib/CodeGen > directory. If you change other parts, a make from LLVMOBJDIR will > synchronize it. > > Try adding code like this to your Passes.cpp file: > > > //===--------------------------------------------------...

...ve unpacked llvm-gcc-4.2-2.6.source.tar.gz under the llvm-gcc >> directory. I've also created two subdirectories >> called "install" and "obj" under the same llvm-gcc. >> >> 3. Then I did the following, based on README.LLVM : >> >> %setenv LLVMOBJDIR /home/eliseuf/llvm/llvm-gcc/obj > > first you need to build llvm itself. LLVMOBJDIR points to where you > built llvm, not where you are planning to build llvm-gcc. > > Ciao, > > Duncan. > _______________________________________________ > LLVM Developers mailing list &...

Hello Gordon Thank you for your reply When I tried building llvm-gcc from source I got the error: You must specify valid path to your LLVM tree with --enable-llvm=DIR I have tried setting $LLVMOBJDIR to the llvm folder, llvm/Release and llvm/bin, but I still get the same error. Scott -------------------------------------- For All Sports Lovers! SPORTS OHEN PROJECT 2008 http://pr.mail.yahoo.co.jp/yells/

...end on a i686-linux-gnu too. As I notice, if the llvm "tools-only " was build with srcdir != objdir , the building of llvm-gcc4-1.7.source encountered mistakes of unable to find some header files. So I just edited llvm-gcc4-1.7.source/gcc/Makefile.in and a line like this: INCLUDES += -I$(LLVMOBJDIR)/include With this change, the building errors were gone. Is this the right hack? Thanks. Nai On Friday 28 April 2006 08:05, Chris Lattner wrote: > On Fri, 21 Apr 2006, [UTF-8] Rafael Esp?ndola wrote: > > To work aroud the problem I edited gcc/objc/config-lang.in and removed > >...

...f llvm-gcc4 produces: make[1]: *** No rule to make target `llvm-backend.c', needed by `llvm-backend.o'. Stop. While the gcc/Makefile.in has: llvm-backend.o : llvm-backend.cpp $(ALL_HEADERS) #line 2440 it also has: # APPLE LOCAL begin LLVM #line 1018 ifneq ($(LLVMOBJDIR),) OBJS-common += llvm-backend.o llvm-convert.o llvm-types.o llvm-debug.o endif and # FIXME: writing proper dependencies for this is a *LOT* of work. libbackend.o : $(OBJS-common:.o=.c) $(out_file) \ #line 2468 I think the problem is that since llvm-backend.o is in OBJS-common and that is use...

Hi! I'm installing LLVM under Debian Linux. I've installed llvm-gcc3 binaries and am trying to build LLVM. I run make command from llvmobjdir and it builds Release configuration. I didn't set ENABLE_OPTIMIZED variable to 1 and I didn't configure LLVM with --enable-optimized switch. What can cause building Release configuration and how can I switch to Debug one? Thanks. Tony. -- Nae king! Nae quin! Nae laird! Nae master! We wi...

Hi! I'm trying to run llvm-test (current CVS head) with the following command: $LLVMOBJDIR/projects/llvm-test$ make TEST=llc report I run into the following error: make[5]: Entering directory `$LLVMOBJDIR/projects/llvm-test/SingleSource/UnitTests/Vector/SSE' make[5]: *** No rule to make target `Output/sse.expandfft.linked.rbc', needed by `Output/sse.expandfft.linked.bc'. S...

...s with LLVM-GCC 4.0 > Front End source, but got the following error when compiling: > > configure: error: You must specify valid path to your LLVM tree with > --enable-llvm=DIR > make: *** [configure-gcc] Error 1 > > I've done the following in csh before hand: > $ setenv LLVMOBJDIR /home/napi/proj/c2jvm/llvm/llvm-gcc/obj > > Where did I go wrong? > Hi Napi, I always just specify it with the "--enable-llvm" command instead of an environment variable. The doc might be wrong in this instance... -bw

...CC_3.3 GCC_3.3.1 GCC_3.4 GCC_3.4.2 GCC_4.0.0 GCC_4.2.0 It is just the LD_LIBRARY_PATH that brings in the "llvm" libgcc_s.so.1 that breaks the compilation. I added this to my build script and now llvm builds properly. cd build ../llvm-gcc4/configure --prefix=$LLVM/install --enable-llvm=$LLVMOBJDIR --enable-languages=c --disable-threads sed -i 's/LD_LIBRARY_PATH/DUMMY_LD_LIBRARY_PATH_DUMMY/g' Makefile make make install The bugreport mentions this, but since the Makefile is not there before make, one save oneself an make/make clean trip. Hopefully it helps someone that is fighting wi...