similar to: [LLVMdev] .ll test cases for tail call optimization in test-suite

On Tue, Jan 05, 2010 at 04:43:33PM +0300, Gregory Petrosyan wrote: > 'make TEST=example' works, 'make TEST=jit' and 'make' work too. Any ideas about what is going wrong here? No idea why this stuff was there... Index: TEST.libcalls.Makefile =================================================================== --- TEST.libcalls.Makefile (revision 92512) +++

> llvm-ld: error: Cannot find library 'c' I'm using this hack, but of course there should really be a correct fix for this "gcc multi-arch" issue. --- test-suite/Makefile.programs (revision 134059) +++ test-suite/Makefile.programs (working copy) @@ -362,6 +362,7 @@ # Disable asm-verbose. This can slow down compilation and is not what the # compilers default to

On Jan 5, 2010, at 6:22 AM, Gregory Petrosyan wrote: > On Tue, Jan 05, 2010 at 04:43:33PM +0300, Gregory Petrosyan wrote: >> 'make TEST=example' works, 'make TEST=jit' and 'make' work too. Any >> ideas about what is going wrong here? > > No idea why this stuff was there... looks like some lines got moved, fixed on mainline, thanks. -Chris >

On Tue, Jan 05, 2010 at 10:05:21AM -0800, Chris Lattner wrote: > looks like some lines got moved, fixed on mainline, thanks. Not really fixed :-) Please commit this: Index: TEST.libcalls.Makefile =================================================================== --- TEST.libcalls.Makefile (revision 92749) +++ TEST.libcalls.Makefile (working copy) @@ -23,10 +23,10 @@

Hello, Apple's GCC does not make the distinction between .s and .S files and always run the preprocessor. From the man: | file.s | Assembler code. Apple's version of GCC runs the preprocessor on these | files as well as those ending in .S. | | file.S | Assembler code which must be preprocessed. The problem is that sometimes llc generates comments in the assembly that

This is what I get while trying to run 'make TEST=libcalls' in the top dir of test-suite: make[1]: Entering directory `/home/gregory/thesis/llvm/projects/test-suite/SingleSource' make[2]: Entering directory `/home/gregory/thesis/llvm/projects/test-suite/SingleSource/UnitTests' make[3]: Entering directory

On 12 Oct 2007, at 07:07, Evan Cheng wrote: >>In order to test the tail call optimization i created quite a few >>.ll files and added them to the SingleSource directory in the >>test-suite. For example >>llvm-test/SingleSource/Tailcall/tailcall1-2.ll. >Shouldn't these be dejagnu tests instead? There is one test in dejagnu that tests whether tail call optimization

On Sun, 4 Sep 2005, Tanu Sharma wrote: > > I have a doubt. > > This is an excerpt of the raw report I get after running Spec benchmarks > through llvm-test.I am trying to calculate the program execution > time.Does the output result in bold corresponds to "lli time" in > Makefile.spec ? I am not interested in llc, jit or cbe.I simply need the > normal

I have a doubt. This is an excerpt of the raw report I get after running Spec benchmarks through llvm-test.I am trying to calculate the program execution time.Does the output result in bold corresponds to "lli time" in Makefile.spec ? I am not interested in llc, jit or cbe.I simply need the normal bytecode and native code execution times after running my pass over them.I have modified

Very true, but we do want the testsuite to run fast. Can it be sped up? -Chris On Dec 12, 2010, at 10:57 AM, Anton Korobeynikov <anton at korobeynikov.info> wrote: >> Maybe this should be off by default? > It's off by default on any user-visible tools (e.g. clang / llvm-gcc). > Since llc is a developer tool it does make sense to enable verbose > output by default. >

> Very true, but we do want the testsuite to run fast.  Can it be sped up? Can't we just run testsuite with asm-verbose=0 ? -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

Doh, thanks, done. -Chris On Jan 5, 2010, at 11:27 AM, Gregory Petrosyan wrote: > On Tue, Jan 05, 2010 at 10:05:21AM -0800, Chris Lattner wrote: >> looks like some lines got moved, fixed on mainline, thanks. > > Not really fixed :-) Please commit this: > > Index: TEST.libcalls.Makefile > =================================================================== > ---

My source directory wasn't correct but now I have a correct test directory structure. $ls -1 ~/tmp/speccpu2000/benchspec/CINT2000/164.gzip/ data docs exe result run Spec src version I reconfigured the llvm with ../configure --prefix=/home/dskhudia/tmp/llvm-install --with-llvmgccdir=/home/dskhudia/tmp/llvm-install --with-externals=/home/dskhudia/tmp Now I can execute the make -C 164.gzip but

> 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

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

Hi Duncan, Do you have sources also in the $LLVM_SRC_ROOT/projects/test-suite/External/SPEC/CINT2000/164.gzip? The following is content of above directory in my case. I have copied the CINT2000 sources in this directory manually. $ls -1 $LLVM_SRC_ROOT/projects/test-suite/External/SPEC/CINT2000/164.gzip 164.gzip.reference_output 164.gzip.reference_output.small compile_info compile_parms

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

Hi, I am currently trying to set up new performance and regression testers for Polly and LLVM and would like to XFAIL two test cases. I am using the LNTBuilder instead of the NightlyTestBuilder out of the assumption that the LNTBuilder is the more modern solution. However, when trying to xfail test cases I realized the xfail=[] parameter of getLNTFactor is ignored. Previously this was not an

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

Another round ;) Sadly not beer. tested against r42630 darwin-x86: SPASS llc-beta still fails thanks for the patience On 5 Oct 2007, at 20:58, Evan Cheng wrote: > Yes please. >> okay then i'll make tailcallopt switch stack adjusting behaviour? the patch for the test suite (when/if it's needed) would be something like: >>>>> --- Makefile.programs (revision