search for: suited

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

TL;DR: I am proposing to add the GCC C Torture suite [1], as an additional external source of tests for the “nightly” test suite. If you are willing to review the patch, it is here: https://reviews.llvm.org/D66887 Background: While working on the RISC-V backend, we have found it useful to use additional test suites beyond the in-tree Clang and LLVM tests and the LLVM nightly tests, in order to

Hi, I'm trying to run the tests in llvm-suite, but I've run into trouble. First, I had the llvm-suite checkout in a directory alongside the llvm compiler checkout, but, when I ran "make" from llvm-suite, it complained about there not being a Makefile two levels above it, so I moved llvm-suite into the "test" subdirectory inside the llvm compiler checkout. I ran

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

On Fri, 30 Aug 2019 at 17:34, Finkel, Hal J. via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > > On 8/30/19 10:18 AM, Sam Elliott via llvm-dev wrote: > > TL;DR: I am proposing to add the GCC C Torture suite [1], as an additional external source of tests for the “nightly” test suite. If you are willing to review the patch, it is here: https://reviews.llvm.org/D66887 >

2009/3/28 John Mosby <ojomojo at gmail.com> > Thanks Duncan, > I figured it out after a couple of tries, but the docs are not as clear as > your instructions. If there's no specific maintainer of TestingGuide.html, > I'd be happy to update the docs to be as clear as your instructions. > > llvm/projects/Makefile filters out "test-suite" and

There are 1500 tests total, and about 100 on the platform-agnostic blacklist. Alex and I do not think this is an onerous burden for maintenance, either as an external test suite or if the test suite is imported. In the long term, if we import the tests, we know we will have to do updates when the Embecosm work lands, and beyond that updates can be more sporadic. It’s not clear to me how much

Hi all, I would like to get some feedback on who in the community is using the LLVM test-suite repository, and in what ways. I am talking specifically about the "test-suite" SVN project, e.g.: http://llvm.org/svn/llvm-project/test-suite/trunk/ not about the "test (no-dash) suite" that is part of LLVM. If you are using the LLVM test-suite project directly (as opposed to via

[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

Hi all, as you might have seen, I just did some restructuring on the testing documentation. Since the changes are only documentation and mostly text movement, I took the liberty of committing without posting a patch first. Was that appropriate?. The incentive for this commit was that I've spent the last week trying to get a grip on the test suite with moderate success. I think this

Hi, I can no longer connect to Dovecot (IMAP). The connection is terminated by Dovecot after Client Helo. My server: Dovecot 2.3.3 Debian buster/sid Architecture: ppc My problems started in late August after upgrading Dovecot. SSL settings: ssl_dh = </etc/ssl/dh2048.pem ssl_min_protocol = TLSv1.2 ssl_cipher_list =

Thanks Duncan, I figured it out after a couple of tries, but the docs are not as clear as your instructions. If there's no specific maintainer of TestingGuide.html, I'd be happy to update the docs to be as clear as your instructions. llvm/projects/Makefile filters out "test-suite" and "llvm-test" when builds are done, so it looks like those two names work. John On

> On Feb 24, 2016, at 1:43 PM, Joerg Sonnenberger via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > On Wed, Feb 24, 2016 at 02:20:24PM -0700, Jonathan Roelofs via llvm-dev wrote: >> 2) There is the cap on total repository size, which is in the neighborhood >> of 1Gb [3]. A fresh checkout of test-suite clocks in at just over 3Gb. This >> one actually is a

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)

I want to push a change to llvm-test-suite, but I don't know how and must be missing something really obvious here. This is what I did, and what I am getting: $ git clone https://<username>@github.com/llvm/llvm-test-suite.git $ git apply mypatch.diff $ git push origin master Password for 'https://<username>@github.com': remote: Permission to llvm/llvm-test-suite.git

Please email the list, not me directly. Try doing a 'make clean' then a 'make VERBOSE=1' in the test-suite directory. -Chris On Jan 13, 2011, at 6:04 PM, Qingan Li wrote: > Hi Chris, > > [qali at qali SingleSource]$ llvm-gcc -v > Using built-in specs. > Target: x86_64-unknown-linux-gnu > Configured with: /home/nicholas/2.8-final/llvmgcc42-2.8.src/configure

Dear community, LLVM test-suite includes both default applications (benchmarks, tests) and test harness (CMake modules, lit-support, some scripts, etc.). Test suite provides extension interface to add "external" tests suite and folders. This worked well, we enhanced basic harness and integrated large set of internal benchmarks and applications. However, we have users interested in LLVM

I'm trying to run test-suite for x86 in order to verify a target independent patch before I put it back. The patch has been approved. What is the best way to run it in order to get maximum coverage and have results where I can tell that I have not regressed anything (as well as the test-suite can help with that)? I've already tested it against the Mips compiler but we have a slightly

I'm getting three failures. TEST-FAIL: exec /home/rkotler/llvmpb3/build/projects/test-suite/SingleSource/UnitTests/Vector/SSE/sse.expandfft TEST-RESULT-exec-time: user 0.3200 TEST-RESULT-exec-real-time: real 0.3172 TEST-FAIL: exec /home/rkotler/llvmpb3/build/projects/test-suite/SingleSource/UnitTests/Vector/SSE/sse.stepfft TEST-RESULT-exec-time: user 0.4000

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