Displaying 20 results from an estimated 7000 matches similar to: "[LLVMdev] .ll test cases for tail call optimization in test-suite"
2007 Oct 11
1
[LLVMdev] .ll test cases for tail call optimization in test-suite
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.
Since i don't want opt to inline the tailcalls away :) i changed the rules
in the Makefile situated in the TailCall directory.
I want to compare the output of a file compile with normal llc with
2006 Nov 16
0
[LLVMdev] 1.9 Prerelease Available for Testing
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.
*
2007 Sep 11
2
[LLVMdev] RFC: Tail call optimization X86
Begin forwarded message:
> From: Evan Cheng <evan.cheng at apple.com>
> Date: 11 September 2007 19:26:39 GMT+02:00
> To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu>
> Subject: Re: [LLVMdev] RFC: Tail call optimization X86
> Reply-To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu>
>
> Hi Arnold,
>
> Thanks for the patch. Some questions
2006 Nov 17
2
[LLVMdev] 1.9 Prerelease Available for Testing (TAKE TWO)
Hi Tanya,
Here's my second attempt on Fedora Core 5. The changes this time are:
1. Using GCC 4.0.3 as the compiler
2. Building everything from source (no pre-built binaries used)
BUILD LLVM WITH GCC 4.0.3
* No issues, just the usual warnings.
BUILD LLVM-GCC WITH GCC 4.0.3
* No issues
RUN LLVM-TEST WITH GCC 4.0.3
* The following failures were encountered. Some of them are
2009 Mar 28
0
[LLVMdev] LLVM test-suite
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
2011 Apr 12
1
[LLVMdev] Problems with test-suite
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
2012 Dec 13
2
[LLVMdev] failures in test-suite for make TEST=simple
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
2009 Feb 07
3
[LLVMdev] Problem Running llvm-suite
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
2013 Aug 12
1
[LLVMdev] [FastPolly]: Update of Polly's performance on LLVM test-suite
At 2013-08-12 01:18:30,"Tobias Grosser" <tobias at grosser.es> wrote:
>On 08/10/2013 06:59 PM, Star Tan wrote:
>> Hi all,
>>
>> I have evaluated Polly's performance on LLVM test-suite with latest LLVM (r188054) and Polly (r187981). Results can be viewed on: http://188.40.87.11:8000.
>
>Hi Star Tan,
>
>thanks for the update.
>
2013 Feb 19
4
[LLVMdev] ARM LNT test-suite Buildbot
Hi Folks,
Looks like our LNT ARM buildbot with the vectorizer is running and
producing good results. There are only 11 failures:
FAIL: MultiSource/Applications/Burg/burg.execution_time (1 of 1104)
FAIL: MultiSource/Applications/ClamAV/clamscan.execution_time (2 of 1104)
FAIL: MultiSource/Applications/lemon/lemon.execution_time (3 of 1104)
FAIL:
2012 Dec 13
0
[LLVMdev] failures in test-suite for make TEST=simple
I forgot to mention that you can also run "make TEST=simple report" which will generate a nice report.
Do you know why these tests fail ? You can step into the test directory and run 'make TEST=simple' from there. It will save you some time.
On Dec 12, 2012, at 4:04 PM, reed kotler <rkotler at mips.com> wrote:
> I'm getting three failures.
>
> TEST-FAIL:
2014 May 04
12
[LLVMdev] [RFC] Benchmarking subset of the test suite
At the LLVM Developers' Meeting in November, I promised to work on isolating a subset of the current test suite that is useful for benchmarking. Having looked at this in more detail, most of the applications and benchmarks in the test suite are useful for benchmarking, and so I think that a better way of phrasing it is that we should construct a list of programs in the test suite that are not
2012 Dec 13
2
[LLVMdev] failures in test-suite for make TEST=simple
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)
2012 Dec 13
0
[LLVMdev] failures in test-suite for make TEST=simple
when I create the report, there are no failures in it. so maybe these
are being filtered for known failures.
On 12/12/2012 05:03 PM, reed kotler wrote:
> 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:
>
2012 Dec 13
1
[LLVMdev] failures in test-suite for make TEST=simple
I use the 'make TEST=simple' as a pre-commit test. I think that everybody should run these tests before committing to LLVM.
On Dec 12, 2012, at 5:06 PM, reed kotler <rkotler at mips.com> wrote:
> when I create the report, there are no failures in it. so maybe these are being filtered for known failures.
>
> On 12/12/2012 05:03 PM, reed kotler wrote:
>> The first
2013 Aug 11
0
[LLVMdev] [FastPolly]: Update of Polly's performance on LLVM test-suite
On 08/10/2013 06:59 PM, Star Tan wrote:
> Hi all,
>
> I have evaluated Polly's performance on LLVM test-suite with latest LLVM (r188054) and Polly (r187981). Results can be viewed on: http://188.40.87.11:8000.
Hi Star Tan,
thanks for the update.
> There are mainly five new tests and each test is run with 10 samples:
> clang (run id = 27): clang -O3
> pollyBasic (run id =
2012 Nov 05
2
[LLVMdev] New benchmark in test-suite
Hi Daniel,
I'm trying to add LivermoreLoops test to the benchmark suite (tar ball
attached), but I'm getting the error below:
--- Tested: 2 tests --
FAIL: SingleSource/Benchmarks/LivermoreLoops/lloops.compile_time (1 of 2)
FAIL: SingleSource/Benchmarks/LivermoreLoops/lloops.execution_time (2 of 2)
When I use the option to only run this test:
--only-test
2013 Aug 11
2
[LLVMdev] [FastPolly]: Update of Polly's performance on LLVM test-suite
Hi all,
I have evaluated Polly's performance on LLVM test-suite with latest LLVM (r188054) and Polly (r187981). Results can be viewed on: http://188.40.87.11:8000.
There are mainly five new tests and each test is run with 10 samples:
clang (run id = 27): clang -O3
pollyBasic (run id = 28): clang -O3 -load LLVMPolly.so
pollyNoGen (run id = 29): pollycc -O3 -mllvm -polly-optimizer=none
2011 Jun 15
0
[LLVMdev] nightly test suite failure: ms_struct-bitfield-init-1.c
On 6 May 2011 09:29, Jay Foad <jay.foad at gmail.com> wrote:
> I've just tried to run the test-suite, for the first time in ages. It
> stops rather abruptly with:
>
> $ make TEST=nightly report report.html
>
> /home/jay/llvm/local/bin/llvm-gcc
> -I/home/jay/llvm/gitobjdir/projects/test-suite/SingleSource/UnitTests
>
2011 May 06
0
[LLVMdev] nightly test suite failure: ms_struct-bitfield-init-1.c
On May 6, 2011, at 1:29 AM, Jay Foad wrote:
> Hi,
>
> I've just tried to run the test-suite, for the first time in ages. It
> stops rather abruptly with:
>
> $ make TEST=nightly report report.html
This is a test that Fariborz has been working on with Clang. It is possible that llvm-gcc is expected to fail it, if this is so, the test can be put in an #ifdef __clang__.