Displaying 20 results from an estimated 134 matches for "shootout".
2006 Nov 17
2
[LLVMdev] 1.9 Prerelease Available for Testing (TAKE TWO)
...ssion/C++/BuiltinTypeInfo
TEST-FAIL: cbe /SingleSource/Regression/C++/BuiltinTypeInfo
TEST-FAIL: llc /SingleSource/Regression/C++/ofstream_ctor
TEST-FAIL: jit /SingleSource/Regression/C++/ofstream_ctor
TEST-FAIL: cbe /SingleSource/Regression/C++/ofstream_ctor
TEST-FAIL: llc /SingleSource/Benchmarks/Shootout-C++/except
TEST-FAIL: jit /SingleSource/Benchmarks/Shootout-C++/except
TEST-FAIL: cbe /SingleSource/Benchmarks/Shootout-C++/except
* The above test fail because llvm-gcc4 doesn't support C++ EH
TEST-FAIL: llc /MultiSource/Applications/oggenc/oggenc
TEST-FAIL: jit /MultiSource/Applications/og...
2006 Nov 16
0
[LLVMdev] 1.9 Prerelease Available for Testing
...-01-23-UnionInit
TEST-FAIL: cbe /SingleSource/UnitTests/2006-01-23-UnionInit
TEST-FAIL: llc /SingleSource/Benchmarks/CoyoteBench/fftbench
TEST-FAIL: jit /SingleSource/Benchmarks/CoyoteBench/fftbench
TEST-FAIL: cbe /SingleSource/Benchmarks/CoyoteBench/fftbench
TEST-FAIL: llc /SingleSource/Benchmarks/Shootout-C++/ackermann
TEST-FAIL: jit /SingleSource/Benchmarks/Shootout-C++/ackermann
TEST-FAIL: cbe /SingleSource/Benchmarks/Shootout-C++/ackermann
TEST-FAIL: llc /SingleSource/Benchmarks/Shootout-C++/ary2
TEST-FAIL: jit /SingleSource/Benchmarks/Shootout-C++/ary2
TEST-FAIL: cbe /SingleSource/Benchmarks/Sho...
2006 Nov 14
5
[LLVMdev] 1.9 Prerelease Available for Testing
LLVMers,
The LLVM 1.9 Prerelease is available for testing:
http://llvm.org/prereleases/1.9/
If anyone can spare some time, please download the appropriate tarballs
for your platform and test the release (at least with make check). I'd
also appreciate any documentation reviews.
Please note that llvm-gcc3 on x86 may not have a clean dejagnu run. You
should see one XPASS for
2018 Apr 26
0
Compare test-suite benchmarks performance complied without TBAA, with default TBAA and with new TBAA struct path
...-C/Pathfinder/PathFinder.test| 0.73 | 0.82 | -1.09 | -1.09 |
|MultiSource/Benchmarks/FreeBench/pifft/pifft.test | -1.36 | -1.38 | 1.93 | 1.93 |
|MultiSource/Benchmarks/Ptrdist/anagram/anagram.test | 17.81 | 17.89 | -16.35 | -16.35 |
|SingleSource/Benchmarks/Shootout/Shootout-hash.test | -9.30 | -10.31 | 0.10 | 0.55 |
|SingleSource/Benchmarks/Shootout/Shootout-lists.test | -2.97 | -2.97 | 8.82 | 8.82 |
|-----------------------------------------------------------------|--------|--------|--------|--------|
There are many test...
2012 Feb 19
2
[LLVMdev] Problem While Running Test Suite
...SingleSource/Regression/C++/EH/function_try_block | * | * |
SingleSource/Regression/C++/EH/simple_rethrow | * | * |
SingleSource/Regression/C++/EH/ConditionalExpr | * | * |
SingleSource/Benchmarks/Shootout/fib2 | * | * |
SingleSource/Benchmarks/Shootout/ackermann | * | * |
SingleSource/Benchmarks/Shootout/ary3 | * | * |
SingleSource/Benchmarks/Shootout/random...
2004 Jun 19
2
[LLVMdev] benchmarking LLVM
Hi all
i took a look into LLVM benchmarks from nightly tester and
ran Shootout tests on my own. Below go just few outlines.
1. results on my AMD AthlonXP and Xeon used by LLVM
team are different sometime. In particular, both Shootout
and Shootout-C++ show great speed up with LLVM (in
comparison to GCC) on ackerman test on my AthlonXP.
But here:
http://llvm.cs.uiu...
2009 Mar 09
2
[LLVMdev] [llvm-testresults] cfarm-x86-64 x86_64 nightly tester results
...=> 1.9921)
> singlesource/Benchmarks/Adobe-C++/stepanov_vector: -171.51% (0.8280 => 2.2481)
> singlesource/Benchmarks/Misc-C++/bigfib: -43.51% (0.5240 => 0.7520)
> singlesource/Benchmarks/Misc-C++/stepanov_container: -110.33% (1.0080 => 2.1201)
> singlesource/Benchmarks/Shootout-C++/wordfreq: -43.20% (0.5000 => 0.7160)
> multisource/Applications/hbd/hbd: -31.91% (1.7801 => 2.3481)
> multisource/Applications/kimwitu++/kc: -18.78% (32.6580 => 38.7903)
> multisource/Applications/minisat/minisat: -72.05% (1.2160 => 2.0921)
> multisource/Benchmarks/P...
2014 Aug 12
4
[LLVMdev] Explicit template instantiations in libc++
Most of libc++ doesn't have explicit template instantiations, which
leads to a pretty significant build time and code size cost when using
libc++, since a large number of common templates will be emitted by the
compiler and coalesced by the linker. Notably, in include/__config, we
have:
#ifndef _LIBCPP_EXTERN_TEMPLATE
#define _LIBCPP_EXTERN_TEMPLATE(...)
#endif
whereas before
2008 Feb 03
0
[LLVMdev] 2.2 Prerelease available for testing
...82 1.66 * 1.88 | 0.99 1.08 n/a n/a
SingleSource/Benchmarks/Misc/whetstone | 0.0323 4596 0.0299 * 0.0289 | 8.19 8.28 6.28 * 6.46 | 0.99 1.30 n/a n/a
SingleSource/Benchmarks/Shootout-C++/ackermann | 0.0081 3944 0.0144 * 0.0141 | 4.12 3.26 3.51 * 3.42 | 1.26 1.17 n/a n/a
SingleSource/Benchmarks/Shootout-C++/ary | 0.0475 4508 0.0143 *...
2007 Sep 18
0
[LLVMdev] 2.1 Pre-Release Available (testers needed)
...23 2.87 * 3.71 | 0.89 1.01 n/a n/a
SingleSource/Benchmarks/Misc/whetstone | 0.0280 4468 0.0400 * 0.0360 | 8.70 8.44 9.15 * 9.32 | 1.03 0.95 n/a n/a
SingleSource/Benchmarks/Shootout-C++/ackermann | 0.0040 2296 0.0120 * 0.0160 | 4.82 3.17 7.19 * 6.78 | 1.52 0.67 n/a n/a
SingleSource/Benchmarks/Shootout-C++/ary | 0.0160 4808 0.0280 *...
2004 Jun 19
0
[LLVMdev] benchmarking LLVM
On Sat, 19 Jun 2004, [koi8-r] "Valery A.Khamenya[koi8-r] " wrote:
> i took a look into LLVM benchmarks from nightly tester and
> ran Shootout tests on my own. Below go just few outlines.
>
> 1. results on my AMD AthlonXP and Xeon used by LLVM
> team are different sometime. In particular, both Shootout
> and Shootout-C++ show great speed up with LLVM (in
> comparison to GCC) on ackerman test on my AthlonXP.
> But here:
&...
2008 Jan 24
6
[LLVMdev] 2.2 Prerelease available for testing
LLVMers,
The 2.2 prerelease is now available for testing:
http://llvm.org/prereleases/2.2/
If anyone can help test this release, I ask that you do the following:
1) Build llvm and llvm-gcc (or use a binary). You may build release
(default) or debug. You may pick llvm-gcc-4.0, llvm-gcc-4.2, or both.
2) Run 'make check'.
3) In llvm-test, run 'make TEST=nightly report'.
4) When
2007 Sep 18
0
[LLVMdev] 2.1 Pre-Release Available (testers needed)
...57 1.60 * 1.87 | 0.95 0.93 n/a n/a
SingleSource/Benchmarks/Misc/whetstone | 0.0314 4472 0.0276 * 0.0287 | 5.62 5.41 5.84 * 5.92 | 1.04 0.96 n/a n/a
SingleSource/Benchmarks/Shootout-C++/ackermann | 0.0060 2228 0.0123 * 0.0117 | 2.53 1.95 3.30 * 3.43 | 1.30 0.77 n/a n/a
SingleSource/Benchmarks/Shootout-C++/ary | 0.0393 4764 0.0277 *...
2008 Jan 28
0
[LLVMdev] 2.2 Prerelease available for testing
...24 1.36 * 1.60 | 0.95 0.87 n/a n/a
SingleSource/Benchmarks/Misc/whetstone | 0.0221 4748 0.0150 * 0.0159 | 0.95 0.92 1.11 * 1.13 | 1.03 0.86 n/a n/a
SingleSource/Benchmarks/Shootout-C++/ackermann | 0.0041 3420 0.0051 * 0.0055 | 1.42 1.54 2.13 * 2.41 | 0.92 0.67 n/a n/a
SingleSource/Benchmarks/Shootout-C++/ary | 0.0191 4588 0.0085 *...
2015 Feb 26
5
[LLVMdev] [RFC] AArch64: Should we disable GlobalMerge?
Hi all,
I've started looking at the GlobalMerge pass, enabled by default on
ARM and AArch64. I think we should reconsider that, at least for
AArch64.
As is, the pass just merges all globals together, in groups of 4KB
(AArch64, 128B on ARM).
At the time it was enabled, the general thinking was "it's almost
free, it doesn't affect performance much, we might as well use it".
2009 Oct 20
1
[LLVMdev] 2.6 pre-release2 ready for testing
... 9.33 | 0.96 1.00 n/a n/a
> SingleSource/Benchmarks/Misc/whetstone |
> 0.0199 3344 0.0199 * 0.0199 | 1.63 1.52
> 1.52 * 1.58 | 1.07 1.07 n/a n/a
> SingleSource/Benchmarks/Shootout-C++/ackermann |
> 0.0499 11044 0.0500 * 0.0400 | 1.14 1.14
> 1.14 * 1.39 | 1.00 1.00 n/a n/a
> SingleSource/Benchmarks/Shootout-C++/ary |
> 0.0300 9120 0.0299 *...
2009 Oct 20
0
[LLVMdev] 2.6 pre-release2 ready for testing
Hi Tanya,
> 1) Compile llvm from source and untar the llvm-test in the projects
> directory (name it llvm-test or test-suite). Choose to use a
> pre-compiled llvm-gcc or re-compile it yourself.
I compiled llvm and llvm-gcc with separate objects directories.
Platform is x86_64-linux-gnu.
> 2) Run make check, report any failures (FAIL or unexpected pass). Note
> that you need to
2009 Oct 20
1
[LLVMdev] 2.6 pre-release2 ready for testing
...| 0.96 1.00 n/a n/a
> SingleSource/Benchmarks/Misc/
> whetstone | 0.0199 3344
> 0.0199 * 0.0199 | 1.63 1.52 1.52
> * 1.58 | 1.07 1.07 n/a n/a
> SingleSource/Benchmarks/Shootout-C++/
> ackermann | 0.0499 11044 0.0500
> * 0.0400 | 1.14 1.14 1.14 *
> 1.39 | 1.00 1.00 n/a n/a
> SingleSource/Benchmarks/Shootout-C++/
> ary | 0.0300 9120...
2007 Sep 15
22
[LLVMdev] 2.1 Pre-Release Available (testers needed)
LLVMers,
The 2.1 pre-release (version 1) is available for testing:
http://llvm.org/prereleases/2.1/version1/
I'm looking for members of the LLVM community to test the 2.1
release. There are 2 ways you can help:
1) Download llvm-2.1, llvm-test-2.1, and the appropriate llvm-gcc4.0
binary. Run "make check" and the full llvm-test suite (make
TEST=nightly report).
2) Download
2009 Oct 17
12
[LLVMdev] 2.6 pre-release2 ready for testing
LLVMers,
2.6 pre-release2 is ready to be tested by the community.
http://llvm.org/prereleases/2.6/
If you have time, I'd appreciate anyone who can help test the release.
To test llvm-gcc:
1) Compile llvm from source and untar the llvm-test in the projects
directory (name it llvm-test or test-suite). Choose to use a pre-
compiled llvm-gcc or re-compile it yourself.
2) Run make check,