search for: llvmcc1plus

On Aug 24, 2007, at 1:52 PM, Holger Schurig wrote: > Is llvmc meant for compilation? > I'm not sure what the status of llvmc is (is anyone working on it?), but I don't believe it was ready for real use or was finished. If you would like to work on it, patches are welcomed! Thanks, Tanya > $ llvmc -c a.c -o a.o > /usr/src/llvm/dist/etc/llvm/c:55: Error: Expecting output

Is llvmc meant for compilation? $ llvmc -c a.c -o a.o /usr/src/llvm/dist/etc/llvm/c:55: Error: Expecting output type value /usr/src/llvm/dist/etc/llvm/c had 1 errors. Terminating. The offending line contains: optimizer.output = bytecode which doesn't seem to be understood by llvmc. If I uncomment this line, I get another error message: $ llvmc -c a.c -o a.o llvmc: Can't find program

> LLVM tools and LLVM-GCC I've built seem to work. > Can it be due to LLVM_SRC_ROOT == LLVM_OBJ_ROOT? No. This is usually due to absence of llvm-gcc. You need reconfigure llvm once again with lvm-gcc path added and make sure it was hooked properly (look into Makefile.config for paths, etc). -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg

...was hooked > properly (look into Makefile.config for paths, etc). As I mentioned, it looks like llvm-gcc is installed properly. From Makefile.config: LLVMGCC := /usr/local/bin/llvm-gcc.exe LLVMGXX := /usr/local/bin/llvm-g++.exe LLVMCC1 := /usr/local/libexec/gcc/i686-pc-cygwin/4.2.1/cc1.exe LLVMCC1PLUS := /usr/local/libexec/gcc/i686-pc-cygwin/4.2.1/cc1plus.exe LLVMGCC_VERSION := 4.2.1 LLVMGCC_MAJVERS := 4 LLVMGCC_LANGS := c,c++ It looks to me that this: make[4]: *** No rule to make target `Output/sse.expandfft.linked.rbc', needed by `Output/sse.expandfft.linked.bc'. Stop. means that m...

...st gcc is 4.4.5. * 2. After the reconfigure process, I have search LLVM in config.log, and all the results are below: [qali at qali llvm-2.8-ori]$ grep "^LLVM" config.log LLVMCC1='/home/qali/build/llvm-gcc4.2-2.8-x86_64-linux/bin/../libexec/gcc/x86_64-unknown-linux-gnu/4.2.1/cc1' LLVMCC1PLUS='/home/qali/build/llvm-gcc4.2-2.8-x86_64-linux/bin/../libexec/gcc/x86_64-unknown-linux-gnu/4.2.1/cc1plus' LLVMCC_OPTION='llvm-gcc' LLVMGCC='/home/qali/build/llvm-gcc4.2-2.8-x86_64-linux/bin/llvm-gcc' LLVMGCCCOMMAND='/home/qali/build/llvm-gcc4.2-2.8-x86_64-linux/bin/llvm-...

..."$as_me:$LINENO: checking llvm-gcc component support" >&5 echo $ECHO_N "checking llvm-gcc component support... $ECHO_C" >&6; } - llvmcc1path=`"$LLVMGCC" --print-prog-name=cc1` + llvmcc1path=`$LLVMGCC --print-prog-name=cc1` LLVMCC1=$llvmcc1path - llvmcc1pluspath=`"$LLVMGCC" --print-prog-name=cc1plus` + llvmcc1pluspath=`$LLVMGCC --print-prog-name=cc1plus` LLVMCC1PLUS=$llvmcc1pluspath llvmgccdir=`echo "$llvmcc1path" | sed 's,/libexec/.*,,'` LLVMGCCDIR=$llvmgccdir - llvmgcclangs=`"$LLVMGCC" -v --help 2...

...='' INSTALL_PROGRAM='' INSTALL_SCRIPT='' JIT='' LDFLAGS='-flat-namespace' LEX='' LEXLIB='' LEX_OUTPUT_ROOT='' LIBADD_DL='' LIBOBJS='' LIBS='' LIBTOOL='' LINKALL='-Wl,-all_load' LLVMCC1='' LLVMCC1PLUS='' LLVMGCC='' LLVMGCCDIR='' LLVMGCCLIBEXEC='' LLVMGCC_LANGS='' LLVMGCC_MAJVERS='' LLVMGCC_VERSION='' LLVMGXX='' LLVM_BINDIR='' LLVM_CONFIGTIME='' LLVM_COPYRIGHT='Copyright (c) 2003-2008 University of Illinois at Urb...

After following all steps from http://llvm.org/docs/TestingGuide.html#testsuiterun, I've got this: make[1]: Entering directory `/cygdrive/c/projects/thesis/llvm-suite-2.6/llvm-2.6/projects/test-suite/SingleSource' make[2]: Entering directory `/cygdrive/c/projects/thesis/llvm-suite-2.6/llvm-2.6/projects/test-suite/SingleSource/UnitTests' make[3]: Entering directory

On 11/08/2010 03:18 PM, Duncan Sands wrote: > Hi Tobias, > >> I am very interested in using dragonegg as a fortran frontend for the >> LLVM test >> suite, as a start to improve fortran support. >> >> I believe this should be easy, but when I looked into this I had the >> impression >> the nightly tester in the llvm test-suite does not even support

...#39; > JIT='' > LDFLAGS='-flat-namespace' > LEX='' > LEXLIB='' > LEX_OUTPUT_ROOT='' > LIBADD_DL='' > LIBOBJS='' > LIBS='' > LIBTOOL='' > LINKALL='-Wl,-all_load' > LLVMCC1='' > LLVMCC1PLUS='' > LLVMGCC='' > LLVMGCCDIR='' > LLVMGCCLIBEXEC='' > LLVMGCC_LANGS='' > LLVMGCC_MAJVERS='' > LLVMGCC_VERSION='' > LLVMGXX='' > LLVM_BINDIR='' > LLVM_CONFIGTIME='' > LLVM_COPYRIGHT='Cop...

...st gcc is 4.4.5. * 2. After the reconfigure process, I have search LLVM in config.log, and all the results are below: [qali at qali llvm-2.8-ori]$ grep "^LLVM" config.log LLVMCC1='/home/qali/build/llvm-gcc4.2-2.8-x86_64-linux/bin/../libexec/gcc/x86_64-unknown-linux-gnu/4.2.1/cc1' LLVMCC1PLUS='/home/qali/build/llvm-gcc4.2-2.8-x86_64-linux/bin/../libexec/gcc/x86_64-unknown-linux-gnu/4.2.1/cc1plus' LLVMCC_OPTION='llvm-gcc' LLVMGCC='/home/qali/build/llvm-gcc4.2-2.8-x86_64-linux/bin/llvm-gcc' LLVMGCCCOMMAND='/home/qali/build/llvm-gcc4.2-2.8-x86_64-linux/bin/llvm-...

*1. I have searched the access/setting of LLVMCC_EMITIR_FLAG in the build directory, recursively, and all the output is what I pasted in last email (just the same to the that in source directory). Maybe the configure failed to do it. My command list for building the test suit is as followings:* *(1) cd ~/SRC_DIR/llvm/projects* *(2) svn co http://llvm.org/svn/llvm-project/test-suite/trunk