search for: llvmcc_emitir_flag

*[qali at qali llvm-2.8-rev]$ find . -exec grep -n "LLVMCC_EMITIR_FLAG" ./ {} \;* ./projects/test-suite/Makefile.tests:47: -$(LCC) $(CPPFLAGS) $(CFLAGS) $(LOPTFLAGS) $(X_TARGET_FLAGS) -S $< -o $@ $(LLVMCC_EMITIR_FLAG) ./projects/test-suite/Makefile.tests:51: -$(LCXX) $(CPPFLAGS) $(CXXFLAGS) $(LOPTFLAGS) $(X_TARGET_FLAGS) -S $< -o $@ $(LLVMCC_EMITIR_FLAG) ./...

On Jan 15, 2011, at 8:06 PM, Qingan Li wrote: > [qali at qali llvm-2.8-rev]$ find . -exec grep -n "LLVMCC_EMITIR_FLAG" ./ {} \; > ./projects/test-suite/Makefile.tests:47: -$(LCC) $(CPPFLAGS) $(CFLAGS) $(LOPTFLAGS) $(X_TARGET_FLAGS) -S $< -o $@ $(LLVMCC_EMITIR_FLAG) > ./projects/test-suite/Makefile.tests:51: -$(LCXX) $(CPPFLAGS) $(CXXFLAGS) $(LOPTFLAGS) $(X_TARGET_FLAGS) -S $< -o $@ $(LLVMCC_EMITIR...

*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...

...Src/llvm-2.8/configure --prefix=/home/qali/install/llvm-2.8 --enable-debug-runtime --disable-optimized --enable-debug-symbols --enable-assertions --with-llvmgccdir=/home/qali/install/llvm-gcc4.2-2.8-x86_64-linux * // reconfigure process* (11) grep EMITIR * Here, I get no results. It seems LLVMCC_EMITIR_FLAG was not set during my configuration. My linux is Fedora Core 13, cpu is intel i3, and host 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-2.8-rev/Debug+Asserts/bin/llvm-as: Output/sse.expandfft.ll:1:2: error: expected top-level entity > .file "/home/qali/Src/llvm-2.8/projects/test-suite/SingleSource/UnitTests/Vector/SSE/sse.expandfft.c" Something is odd here. Can you do a grep in your top-level build directory for LLVMCC_EMITIR_FLAG? It's obviously blank and it shouldn't be. You should take a look at the configure output and see what happened. -eric -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20110113/c08798b1/attachment.html...

[qali at qali test-suite]$ make VERBOSE=1 if [ ! -f SingleSource/Makefile ]; \ then \ /home/qali/Src/llvm-2.8/autoconf/mkinstalldirs SingleSource; \ cp /home/qali/Src/llvm-2.8/projects/test-suite/SingleSource/Makefile SingleSource/Makefile; \ fi; \ make -C SingleSource all make[1]: Entering directory `/home/qali/build/llvm-2.8-rev/projects/test-suite/SingleSource' if [ ! -f UnitTests/Makefile

...ll -emit-llvm Trouble is, llvm-g++ emits an .ll file which isn't valid so llvm-as fails on my machine. I've looked at the makefiles for the test suite and it seems that this command is the one being run here -$(LCXX) $(CPPFLAGS) $(CXXFLAGS) $(LOPTFLAGS) $(X_TARGET_FLAGS) -S $< -o $@ $(LLVMCC_EMITIR_FLAG) So how did my machine find llvm-g++ for $(LCXX) but the build machine found clang++? Note i have configured my machine and pointed the test-suite at my bin folder as the command after that failing one has the correct path. /Users/pete/svn/Debug+Asserts/bin/llvm-as Output/spirit.ll -o Output/s...

...d49 Author: Daniel Jasper <djasper at google.com> Date: Thu Feb 28 11:05:57 2013 +0000 Improve formatting of #defines. the test-suite patch is against: commit 8c1ab3b660e67b74421d657408167b1345188f8d Author: Duncan Sands <baldrick at free.fr> Date: Sun Feb 17 15:21:11 2013 +0000 Use LLVMCC_EMITIR_FLAG rather than -emit-llvm please review, looking forward to your feedback. thanks. --- Regards, Jiong Tilera Corporation. -------------- next part -------------- A non-text attachment was scrubbed... Name: llvm-tilegx-port.tar.bz2 Type: application/octet-stream Size: 69121 bytes Desc: not availabl...

...echo "${ECHO_T}$llvm_cv_llvmgcc_dragonegg" >&6; } @@ -20598,32 +20596,30 @@ echo $ECHO_N "(cached) $ECHO_C" >&6 else llvm_cv_llvmgcc_sanity="no" -if test -x "$LLVMGCC" ; then cp /dev/null conftest.c - "$LLVMGCC" "$LLVMCC_EMITIR_FLAG" -S -o - conftest.c | \ + $LLVMGCC "$LLVMCC_EMITIR_FLAG" -S -o - conftest.c | \ grep 'target datalayout =' > /dev/null 2>&1 if test $? -eq 0 ; then llvm_cv_llvmgcc_sanity="yes" fi rm conftest.c fi -fi { echo "$as_me:$LIN...

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

...+0000 >> >> Improve formatting of #defines. >> >> the test-suite patch is against: >> >> commit 8c1ab3b660e67b74421d657408167b1345188f8d >> Author: Duncan Sands <baldrick at free.fr> >> Date: Sun Feb 17 15:21:11 2013 +0000 >> >> Use LLVMCC_EMITIR_FLAG rather than -emit-llvm >> >> >> please review, looking forward to your feedback. >> >> thanks. >> >> --- >> Regards, >> Jiong >> Tilera Corporation. >> >> _______________________________________________ >> LLVM Developers...

...> Date: Thu Feb 28 11:05:57 2013 +0000 > > Improve formatting of #defines. > > the test-suite patch is against: > > commit 8c1ab3b660e67b74421d657408167b1345188f8d > Author: Duncan Sands <baldrick at free.fr> > Date: Sun Feb 17 15:21:11 2013 +0000 > > Use LLVMCC_EMITIR_FLAG rather than -emit-llvm > > > please review, looking forward to your feedback. > > thanks. > > --- > Regards, > Jiong > Tilera Corporation. > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu...

...Date: Thu Feb 28 11:05:57 > 2013 +0000 > > Improve formatting of #defines. > > the test-suite patch is against: > > commit 8c1ab3b660e67b74421d657408167b1345188f8d > Author: Duncan Sands <baldrick at free.fr> Date: Sun Feb 17 15:21:11 > 2013 +0000 > > Use LLVMCC_EMITIR_FLAG rather than -emit-llvm > > > please review, looking forward to your feedback. > > thanks. > > --- > Regards, > Jiong > Tilera Corporation. > > _______________________________________________ > LLVM Developers mailing list LLVMdev at cs.uiuc.edu > http:...

...Src/llvm-2.8/configure --prefix=/home/qali/install/llvm-2.8 --enable-debug-runtime --disable-optimized --enable-debug-symbols --enable-assertions --with-llvmgccdir=/home/qali/install/llvm-gcc4.2-2.8-x86_64-linux * // reconfigure process* (11) grep EMITIR * Here, I get no results. It seems LLVMCC_EMITIR_FLAG was not set during my configuration. My linux is Fedora Core 13, cpu is intel i3, and host 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...

...+0000 >> >> Improve formatting of #defines. >> >> the test-suite patch is against: >> >> commit 8c1ab3b660e67b74421d657408167b1345188f8d >> Author: Duncan Sands <baldrick at free.fr> Date: Sun Feb 17 15:21:11 >> 2013 +0000 >> >> Use LLVMCC_EMITIR_FLAG rather than -emit-llvm >> >> >> please review, looking forward to your feedback. >> >> thanks. >> >> --- >> Regards, >> Jiong >> Tilera Corporation. >> >> _______________________________________________ >> LLVM Developers...