similar to: [LLVMdev] make TEST=dbgopt donesn't work?

> > Are you able to run nightly test ? > Yes, I can run nightly test. > Here is what I see... > > $ make TEST=dbgopt > /Developer/usr/bin//llvm-gcc sse.expandfft.c -g --emit-llvm -c -o > Output/sse.expandfft.bc > /Volumes/Nanpura/mainline/llvm/Debug/bin/opt Output/sse.expandfft.bc - > strip-nondebug -strip-debug -std-compile-opts -strip -f -o Output/ >

I followed the LNT quickstart guide ( http://llvm.org/docs/lnt/quickstart.html) on my debian machine, and it seems to have a problem running. When I consult test.log, every single test has a section like this # Pretend that the reference output was produced instantaneously. > cp /home/jeremy/hardware/llvm/test-suite/instant.txt > Output/sse.expandfft.out-nat.time >

The attached patch didn't fix it, but when I also changed another == to = a few lines further down it seemed to work. Jeremy On Tue, Jun 24, 2014 at 10:07 PM, Justin Bogner <mail at justinbogner.com> wrote: > Jeremy Salwen <jeremysalwen at gmail.com> writes: > > I followed the LNT quickstart guide > > (http://llvm.org/docs/lnt/quickstart.html) on my debian

Eric Christopher <echristo at apple.com> writes: > On Nov 8, 2011, at 7:20 PM, David A. Greene wrote: > > I couldn't figure out how to run the test-suite. Are there up-to-date > instructions somewhere? llvm-gcc doesn't exist anymore... > > Easiest is to check out the test-suite branch into projects and then after you configure and build from the top

Bill Wendling <wendling at apple.com> writes: > Hi Dave, > > Thanks for the results. What platform is this on? And do these failures occur with 2.9? Platform is Debian Linux testing, x86_64. clang is a disaster with 2.9 unfortunately, so I can't test it: /bin/cp Output/sse.expandfft.llvm.o.compile.time Output/sse.expandfft.simple.compile.time

[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

On Nov 15, 2011, at 9:41 AM, David A. Greene wrote: > Bill Wendling <wendling at apple.com> writes: > >> Hi Dave, >> >> Thanks for the results. What platform is this on? And do these failures occur with 2.9? > > Platform is Debian Linux testing, x86_64. > > clang is a disaster with 2.9 unfortunately, so I can't test it: > > /bin/cp

On Jan 13, 2011, at 6:22 PM, Qingan Li wrote: > make[4]: Entering directory `/home/qali/build/llvm-2.8-rev/projects/test-suite/SingleSource/UnitTests/Vector/SSE' > /home/qali/Src/llvm-2.8/autoconf/mkinstalldirs Output > /dev/null > /home/qali/build/llvm-gcc4.2-2.8-x86_64-linux/bin/llvm-gcc -I/home/qali/build/llvm-2.8-rev/projects/test-suite/SingleSource/UnitTests/Vector/SSE

Hello, all- I am having trouble getting the test suite set up with my download of SPEC2006. I downloaded and installed llvm-gcc, checked out a copy of test-suite in llvm-2.8/projects, and then configured and made llvm: ./configure --enable-debug-runtime --disable-optimized --enable-spec2006=/home/jamiemmt/speccpu2006 --with-externals=/home/jamiemmt make The configure script found the SPEC

Hi sir, I have built the test suits in following steps: 0. $cd LLVM_GCC_DIR; $gunzip --stdout llvm-gcc-4.2-*version*-* platform*.tar.gz | tar -xvf - 1. $cd SRC_DIR/llvm-2.8/projects 2. $svn co http://llvm.org/svn/llvm-project/test-suite/trunk test-suite 3.$cd OBJ_DIR; 4. $SRC_DIR/configure --prefix=INS_DIR --enable-debug-runtime --disable-optimized --enable-debug-symbols

Hi Dave, Thanks for the results. What platform is this on? And do these failures occur with 2.9? -bw On Nov 10, 2011, at 9:51 AM, David A. Greene wrote: > greened at obbligato.org (David A. Greene) writes: > >> Nikola Smiljanic <popizdeh at gmail.com> writes: >> >>> I'm not sure if this makes a difference but I ran this >>> >>> make -j

On Fri, 04 May 2007 14:37:53 +0200 Florian Brandner <fbrandne at mail.tuwien.ac.at> wrote: >hello, > >i've problems running the llvm-test suite using debian linux and make >3.81. it works fine on my laptop, running openSuse and make 3.81. > >i already tried to install make 3.75 and 3.79, both did not work. > >the error message is: > >make[1]: *** No rule to

Hello, I am new in using llvm so I would like to get some help on how to compile test-suite. Assumptions: llvm is in /llvm directory llvm-gcc is in /llvm-4.2-2.4-x86-linux-RHEL4/bin I have tried compiling test-suite and I get the following error: $make make[1]: Entering directory '/llvm/projects/test-suite/SingleSource' make[2]: Entering directory

hello, i've problems running the llvm-test suite using debian linux and make 3.81. it works fine on my laptop, running openSuse and make 3.81. i already tried to install make 3.75 and 3.79, both did not work. the error message is: make[1]: *** No rule to make target `Output/sse.expantfft.bc', needed by `Output/sse.expandfft.linked.rbc'. Stop. using make -p, i see that

First, thanks for testing this! > Here's the results for GNU/Linux, 2.6.18-1.2200.fc5smp (Fedora Core 5) > > HIGH LEVEL COMMENTS > * The llvm-1.9.tar.gz file unpacks to a dir named "llvm". Shouldn't > that be llvm-1.9? We have always labeled the dir just llvm which is fine. If you build llvm it will know its version 1.9. > * LLVM was built in Release mode

On Sun, Dec 13, 2009 at 11:34 AM, Anton Korobeynikov <anton at korobeynikov.info> wrote: >> 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

Reid Spencer wrote: > Have you modified the makefile in any way? Note that sse.expantfft.bc should be sse.expandfft.bc no, did'nt change it. the typo before seems to be an error while copying from the terminal. i've cleaned everything and tried again. this is the messsage: [brandner:/localtmp/brandner/dev/llvm-test:529] make -j1 TEST=nightly 2>&1 | tee report.nightly.raw.out

The first one failed on a diff: ******************** TEST (simple) 'sse.expandfft' FAILED! ******************** Execution Context Diff: /home/rkotler/llvmpb3/build/projects/test-suite/tools/fpcmp: Compared: 1.139094e-07 and 1.159249e-07 abs. diff = 2.015500e-09 rel.diff = 1.738626e-02 Out of tolerance: rel/abs: 1.600000e-02/0.000000e+00 ******************** TEST (simple)

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

Tanya, Here's the results for GNU/Linux, 2.6.18-1.2200.fc5smp (Fedora Core 5) HIGH LEVEL COMMENTS * The llvm-1.9.tar.gz file unpacks to a dir named "llvm". Shouldn't that be llvm-1.9? * LLVM was built in Release mode in all cases * I don't think this is ready for release. In particular the llvm-gcc4 binary seg faults on FC 5 for most of llvm-test programs. *