search for: benchmark

...39;t affect performance much, we might as well use it". Now, it's preventing some link-time optimizations (as acknowledged in one of the FIXMEs). -- Performance impact Overall, it isn't that profitable on the test-suite, and actually degrades performance on a lot of other - "non-benchmark" - projects I tried (where the main reason to use a global is file- or function- static variables, only accessed through a single getter function). Across several runs on the entire test-suite, when disabling the pass, I measured: without LTO, a -0.19% geomean improvement with LTO, a +0.11% g...

...| * | MultiSource/Applications/d/make_dparser | * | * | MultiSource/Applications/SPASS/SPASS | * | * | MultiSource/Applications/oggenc/oggenc | * | * | MultiSource/Benchmarks/VersaBench/bmm/bmm | * | * | MultiSource/Benchmarks/VersaBench/ecbdes/ecbdes | * | * | MultiSource/Benchmarks/VersaBench/beamformer/beamformer | * | * | MultiSource/Benchmarks/VersaBench/dbms/dbms...

Hello, I was interested in how much Type-Based Alias Analysis helps to optimize code. For that purpose, I've compared three sets of benchmarks: compiled without TBAA, compiled with a default TBAA metadata format, and compiled with new TBAA metadata format. As a set of benchmarks, I've used the LLVM test suite (http://llvm.org/docs/TestingGuide.html#test-suite-overview) which has a lot of tests already identified as benchmarks. For s...

...loops. Live ranges that cross a function call and are also used in a hot loop get split so there are no spills in the loop. Long, complicated basic blocks benefit from local live range splitting. The register-starved i386 target benefits the most. This is the change in execution time for the SPEC benchmarks that change by more than 3% (minus means faster, plus slower): Targeting i386: -19.3% 164.gzip -12.5% 433.milc -8.8% 473.astar -7.4% 401.bzip2 -6.4% 183.equake -4.9% 456.hmmer -4.6% 186.crafty -4.6% 188.ammp -4.1% 403.gcc -4.0% 256.bzip2 -3.2% 197.parser -3.1% 175.vpr -3.0% 464.h264ref +6.7% 177....

...+ tests in the testsuite, see below. Note that this tester is often under heavy load due to other users, so take timing results with a pinch of salt (a pinch is about +-10% in my experience with this tester). Ciao, Duncan. > Significant changes in test results: > GCCAS: > singlesource/Benchmarks/Adobe-C++/functionobjects: -102.68% (0.5960 => 1.2080) > singlesource/Benchmarks/Adobe-C++/loop_unroll: -44.04% (5.3323 => 7.6804) > singlesource/Benchmarks/Adobe-C++/simple_types_constant_folding: -10.34% (5.6883 => 6.2763) > singlesource/Benchmarks/Adobe-C++/simple_types_loo...

...;  0.00 *           0.47 | -       -       n/a          n/a > MultiSource/Applications/viterbi/viterbi                                 | > 0.0499 5460     0.0400      *                0.0300      |   11.62   11.68 > 11.81 *          11.87 | 0.99    0.98    n/a          n/a > MultiSource/Benchmarks/ASCI_Purple/SMG2000/smg2000                       | > 2.9899 498940   3.0500      *                2.2999      |    4.51    4.23 >  4.44 *           6.71 | 1.07    1.02    n/a          n/a > MultiSource/Benchmarks/ASC_Sequoia/AMGmk/AMGmk                           | > 0.0999 14168    0....

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

...ass-ordering for Pre-IPO, IPO and Post-IPO phases at this time, and hopefully once for all. In order to repair the image of being a liar, I post some preliminary result in this cozy Saturday afternoon which I normally denote to daydreaming :-) So far I only measure the result of MultiSource benchmarks on my iMac (late 2012 model), and the command to run the benchmark is "make TEST=simple report OPTFLAGS='-O3 -flto'". In terms of execution-time, some degrade, but more improve, few of them are quite substantial. User-time is used for comparison. I measure the result twice,...

...0.47 | - - n/a n/a > MultiSource/Applications/viterbi/ > viterbi | 0.0499 5460 > 0.0400 * 0.0300 | 11.62 11.68 11.81 > * 11.87 | 0.99 0.98 n/a n/a > MultiSource/Benchmarks/ASCI_Purple/SMG2000/ > smg2000 | 2.9899 498940 3.0500 > * 2.2999 | 4.51 4.23 4.44 * > 6.71 | 1.07 1.02 n/a n/a > MultiSource/Benchmarks/ASC_Sequoia/AMGmk/ > AMGmk | 0.0...

...0.00 0.00 0.00 * 0.62 | - - n/a n/a MultiSource/Applications/viterbi/viterbi | 0.0542 6944 0.0405 * 0.0393 | 21.15 38.19 19.29 * 19.40 | 0.55 1.10 n/a n/a MultiSource/Benchmarks/ASCI_Purple/SMG2000/smg2000 | 3.4553 637348 4.8566 * 4.0849 | 10.71 12.59 10.20 * 14.23 | 0.85 1.05 n/a n/a MultiSource/Benchmarks/Fhourstones-3.1/fhourstones3.1 | 0.0767 10752 0.0642 *...

...0.00 0.00 0.00 * 0.67 | - - n/a n/a MultiSource/Applications/viterbi/viterbi | 0.0560 7044 0.0480 * 0.0440 | 22.23 37.97 23.59 * 23.68 | 0.59 0.94 n/a n/a MultiSource/Benchmarks/ASCI_Purple/SMG2000/smg2000 | 4.5362 620828 7.2964 * 6.2523 | 22.45 29.95 23.41 * 31.07 | 0.75 0.96 n/a n/a MultiSource/Benchmarks/Fhourstones-3.1/fhourstones3.1 | 0.0680 10208 0.0640 *...

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

.... Based on my performance measurements (below) I would like to enable the SLP-vectorizer by default on -O3. I would like to hear what others in the community think about this and give other people the opportunity to perform their own performance measurements. — Performance Gains — SingleSource/Benchmarks/Misc/matmul_f64_4x4 -53.68% MultiSource/Benchmarks/Olden/power/power -18.55% MultiSource/Benchmarks/TSVC/LoopRerolling-flt/LoopRerolling-flt -14.71% SingleSource/Benchmarks/Misc/flops-6 -11.02% SingleSource/Benchmarks/Misc/flops-5 -10.03% MultiSource/Benchmarks/TSVC/LinearDependence-flt/LinearD...

Andy and I briefly discussed this the other day, we have not yet got chance to list a detailed pass order for the pre- and post- IPO scalar optimizations. This is wish-list in our mind: pre-IPO: based on the ordering he propose, get rid of the inlining (or just inline tiny func), get rid of all loop xforms... post-IPO: get rid of inlining, or maybe we still need it, only

...ource/Regression/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/Appli...

...0.01 0.00 0.00 * 0.63 | - - n/a n/a MultiSource/Applications/viterbi/viterbi | 0.0455 7084 0.0391 * 0.0384 | 14.87 22.99 18.32 * 18.38 | 0.65 0.81 n/a n/a MultiSource/Benchmarks/ASCI_Purple/SMG2000/smg2000 | 2.9651 620820 4.2171 * 3.6177 | 10.00 13.34 10.16 * 13.94 | 0.75 0.98 n/a n/a MultiSource/Benchmarks/Fhourstones-3.1/fhourstones3.1 | 0.0694 10680 0.0606 *...

...0.00 0.00 0.00 * 0.32 | - - n/a n/a MultiSource/Applications/viterbi/viterbi | 0.0217 7144 0.0361 * 0.0188 | 16.62 15.39 16.72 * 15.80 | 1.08 0.99 n/a n/a MultiSource/Benchmarks/ASCI_Purple/SMG2000/smg2000 | 1.6765 656504 2.1414 * 1.8888 | 7.45 7.88 7.76 * 9.69 | 0.95 0.96 n/a n/a MultiSource/Benchmarks/Fhourstones-3.1/fhourstones3.1 | 0.0464 11496 0.0336 *...

...-01-23-InitializedBitField TEST-FAIL: compile /SingleSource/UnitTests/2006-01-23-UnionInit TEST-FAIL: llc /SingleSource/UnitTests/2006-01-23-UnionInit TEST-FAIL: jit /SingleSource/UnitTests/2006-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/...

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,

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