search for: ldecod

...* * * * | 0.1900 * *And the raw file for nightly contains the following messages - * --------------------------------------------------------------- >>> ========= '/home/arnie/llvm/llvm-obj/projects/test-suite/MultiSource/Applications/JM/ldecod/ldecod' Program --------------------------------------------------------------- TEST-RESULT-nat-time: program 0.060000 TEST-FAIL: llc /home/arnie/llvm/llvm-obj/projects/test-suite/MultiSource/Applications/JM/ldecod/ldecod TEST-FAIL: compile /home/arnie/llvm/llvm-obj/projects/test-suite/Multi...

...* * * * | 0.1900 * *And the raw file for nightly contains the following messages - * --------------------------------------------------------------- >>> ========= '/home/arnie/llvm/llvm-obj/projects/test-suite/MultiSource/Applications/JM/ldecod/ldecod' Program --------------------------------------------------------------- TEST-RESULT-nat-time: program 0.060000 TEST-FAIL: llc /home/arnie/llvm/llvm-obj/projects/test-suite/MultiSource/Applications/JM/ldecod/ldecod TEST-FAIL: compile /home/arnie/llvm/llvm-obj/projects/test-suite/Multi...

...oint me to a good compilation time benchmark I can get some >> figures. >> > I normally use 403.gcc, but if you don't have SPEC sources, these tests in the nightly test suite take a while to compile: > > MultiSource/Applications/ClamAV > MultiSource/Applications/JM/ldecod > MultiSource/Applications/JM/lencod > MultiSource/Applications/SPASS > MultiSource/Applications/kimwitu++/kc > MultiSource/Applications/sqlite3/sqlite3 > > If you run 'make TEST=nightly', both llc and opt compile times are interesting. The runtime of opt is cryptically re...

...e on Linux. Each group of failing tests below is followed by a comment about why its failing. llc /MultiSource/Applications/oggenc/oggenc jit /MultiSource/Applications/oggenc/oggenc cbe /MultiSource/Applications/oggenc/oggenc ^^ no idea what's causing these jit /MultiSource/Applications/JM/ldecod/ldecod ^^ weird jit codegen problem produces wrong FP output, PR963 llc /MultiSource/Applications/JM/lencod/lencod jit /MultiSource/Applications/JM/lencod/lencod cbe /MultiSource/Applications/JM/lencod/lencod ^^ no idea jit /MultiSource/Applications/obsequi/Obsequi ^^ no idea cbe /MultiSou...

...because llvm-gcc4 doesn't support C++ EH TEST-FAIL: llc /MultiSource/Applications/oggenc/oggenc TEST-FAIL: jit /MultiSource/Applications/oggenc/oggenc TEST-FAIL: cbe /MultiSource/Applications/oggenc/oggenc * Not sure, difference in binary output. TEST-FAIL: jit /MultiSource/Applications/JM/ldecod/ldecod * Weird JIT problem, there's a PR filed on this. TEST-FAIL: llc /MultiSource/Applications/JM/lencod/lencod TEST-FAIL: jit /MultiSource/Applications/JM/lencod/lencod TEST-FAIL: cbe /MultiSource/Applications/JM/lencod/lencod * Not sure, difference in numerical output TEST-FAIL: jit /...

On Mar 24, 2011, at 7:23 AM, José Fonseca wrote: >>> >> I normally use 403.gcc, but if you don't have SPEC sources, these tests in the nightly test suite take a while to compile: >> >> MultiSource/Applications/ClamAV >> MultiSource/Applications/JM/ldecod >> MultiSource/Applications/JM/lencod >> MultiSource/Applications/SPASS >> MultiSource/Applications/kimwitu++/kc >> MultiSource/Applications/sqlite3/sqlite3 >> >> If you run 'make TEST=nightly', both llc and opt compile times are interesting. The runtime...

...7:23 AM, José Fonseca wrote: >>>> >>> I normally use 403.gcc, but if you don't have SPEC sources, these >>> tests in the nightly test suite take a while to compile: >>> >>> MultiSource/Applications/ClamAV >>> MultiSource/Applications/JM/ldecod >>> MultiSource/Applications/JM/lencod >>> MultiSource/Applications/SPASS >>> MultiSource/Applications/kimwitu++/kc >>> MultiSource/Applications/sqlite3/sqlite3 >>> >>> If you run 'make TEST=nightly', both llc and opt compile times are...

...http://llvm.org/perf/db_default/v4/nts/1283/graph?test.392=3> 2.22% 4.3907 > 4.4882 0.0010 1.55% 0.0010 > MultiSource/Applications/lua/lua > <http://llvm.org/perf/db_default/v4/nts/1283/graph?test.155=3> 2.18% 1.4158 > 1.4467 0.0010 1.39% 0.0010 > MultiSource/Applications/JM/ldecod/ldecod > <http://llvm.org/perf/db_default/v4/nts/1283/graph?test.125=3> 2.13% 2.1580 > 2.2040 0.0005 1.79% 0.0005 > MultiSource/Applications/d/make_dparser > <http://llvm.org/perf/db_default/v4/nts/1283/graph?test.134=3> 2.12% 1.0745 > 1.0973 0.0005 1.78% 0.0005 > Mult...

...arks/Prolangs-C/simulator/Output/simulator -5.3% MultiSource/Applications/hexxagon/Output/hexxagon -5.2% MultiSource/Applications/SIBsim4/Output/SIBsim4 -4.8% MultiSource/Benchmarks/MallocBench/cfrac/Output/cfrac -4.1% MultiSource/Applications/d/Output/make_dparser -4.0% MultiSource/Applications/JM/ldecod/Output/ldecod -3.9% External/Nurbs/Output/nurbs -3.7% MultiSource/Benchmarks/Ptrdist/bc/Output/bc -3.4% MultiSource/Applications/lemon/Output/lemon -3.4% SingleSource/Benchmarks/Misc-C++/Output/bigfib -3.4% External/SPEC/CFP2000/183.equake/Output/183.equake -3.2% MultiSource/Applications/hbd/Output...

...ilation time. > > If you can point me to a good compilation time benchmark I can get some > figures. I normally use 403.gcc, but if you don't have SPEC sources, these tests in the nightly test suite take a while to compile: MultiSource/Applications/ClamAV MultiSource/Applications/JM/ldecod MultiSource/Applications/JM/lencod MultiSource/Applications/SPASS MultiSource/Applications/kimwitu++/kc MultiSource/Applications/sqlite3/sqlite3 If you run 'make TEST=nightly', both llc and opt compile times are interesting. The runtime of opt is cryptically reported in the GCCAS column....

.../db_default/v4/nts/1283/graph?test.392=3> 2.22% 4.3907 >> 4.4882 0.0010 1.55% 0.0010 >> MultiSource/Applications/lua/lua >> <http://llvm.org/perf/db_default/v4/nts/1283/graph?test.155=3> 2.18% 1.4158 >> 1.4467 0.0010 1.39% 0.0010 >> MultiSource/Applications/JM/ldecod/ldecod >> <http://llvm.org/perf/db_default/v4/nts/1283/graph?test.125=3> 2.13% 2.1580 >> 2.2040 0.0005 1.79% 0.0005 >> MultiSource/Applications/d/make_dparser >> <http://llvm.org/perf/db_default/v4/nts/1283/graph?test.134=3> 2.12% 1.0745 >> 1.0973 0.0005 1....

...283/graph?test.392=3> 2.22% 4.3907 >>> 4.4882 0.0010 1.55% 0.0010 >>> MultiSource/Applications/lua/lua >>> <http://llvm.org/perf/db_default/v4/nts/1283/graph?test.155=3> 2.18% 1.4158 >>> 1.4467 0.0010 1.39% 0.0010 >>> MultiSource/Applications/JM/ldecod/ldecod >>> <http://llvm.org/perf/db_default/v4/nts/1283/graph?test.125=3> 2.13% 2.1580 >>> 2.2040 0.0005 1.79% 0.0005 >>> MultiSource/Applications/d/make_dparser >>> <http://llvm.org/perf/db_default/v4/nts/1283/graph?test.134=3> 2.12% 1.0745 >>&...

...9711 0.0342 > External/SPEC/CINT2006/483_xalancbmk/483_xalancbmk.compile 5.19% 225.5995 > 237.3023 0.6599 > External/SPEC/CINT95/099_go/099_go.compile 5.15% 4.8824 5.1339 0.0061 > MultiSource/Applications/kimwitu++/kc.compile 5.14% 19.5797 20.5852 0.0206 > MultiSource/Applications/JM/ldecod/ldecod.compile 5.13% 7.1410 7.5074 0.0136 > External/SPEC/CINT2006/401_bzip2/401_bzip2.compile 5.09% 2.1246 2.2328 0.0027 > External/SPEC/CINT2006/473_astar/473_astar.compile 5.07% 1.2970 1.3628 0.0028 > SingleSource/Benchmarks/Adobe-C++/loop_unroll.compile 5.07% 3.2894 3.4561 0.0073 >...

On Tue, 2011-03-15 at 20:29 -0700, Jakob Stoklund Olesen wrote: > On Mar 15, 2011, at 4:15 PM, jfonseca at vmware.com wrote: > > > This series of patches address several issues causing memory usage to grow > > indefinetely on a long lived process. > > Thanks for working on this. > > Did you measure the performance impact of these changes? I tracked performance

...> 2.22% 4.3907 >>>> 4.4882 0.0010 1.55% 0.0010 >>>> MultiSource/Applications/lua/lua >>>> <http://llvm.org/perf/db_default/v4/nts/1283/graph?test.155=3> 2.18% 1.4158 >>>> 1.4467 0.0010 1.39% 0.0010 >>>> MultiSource/Applications/JM/ldecod/ldecod >>>> <http://llvm.org/perf/db_default/v4/nts/1283/graph?test.125=3> 2.13% 2.1580 >>>> 2.2040 0.0005 1.79% 0.0005 >>>> MultiSource/Applications/d/make_dparser >>>> <http://llvm.org/perf/db_default/v4/nts/1283/graph?test.134=3> 2.12%...

I created the 1.9 release branch last night. As a reminder, please do not check in any code changes to the release branch. Please send me email if you have changes that need to be merged into the release branch. To check out the release branch: cvs -d <CVS Repository> co -r release_19 llvm cvs -d <CVS Repository> co -r release_19 llvm-test cvs -d <CVS Repository> co -r

...85.00 174.2% test-suite...chmarks/MallocBench/gs/gs.test 57.00 133.00 133.3% test-suite...000/255.vortex/255.vortex.test 95.00 200.00 110.5% test-suite...CFP2006/433.milc/433.milc.test 64.00 134.00 109.4% test-suite...ications/JM/ldecod/ldecod.test 258.00 514.00 99.2% test-suite.../Trimaran/enc-pc1/enc-pc1.test 87.00 168.00 93.1% test-suite...ce/Benchmarks/PAQ8p/paq8p.test 35.00 66.00 88.6% test-suite...INT2000/164.gzip/164.gzip.test 23.00 43.00...

...External/SPEC/CINT2006/483_xalancbmk/483_xalancbmk.compile 5.19% 225.5995 >> 237.3023 0.6599 >> External/SPEC/CINT95/099_go/099_go.compile 5.15% 4.8824 5.1339 0.0061 >> MultiSource/Applications/kimwitu++/kc.compile 5.14% 19.5797 20.5852 0.0206 >> MultiSource/Applications/JM/ldecod/ldecod.compile 5.13% 7.1410 7.5074 0.0136 >> External/SPEC/CINT2006/401_bzip2/401_bzip2.compile 5.09% 2.1246 2.2328 0.0027 >> External/SPEC/CINT2006/473_astar/473_astar.compile 5.07% 1.2970 1.3628 0.0028 >> SingleSource/Benchmarks/Adobe-C++/loop_unroll.compile 5.07% 3.2894 3.4561...

.../Applications/hexxagon/hexxagon TEST-FAIL: cbe /MultiSource/Applications/hexxagon/hexxagon TEST-FAIL: llc /MultiSource/Applications/oggenc/oggenc TEST-FAIL: jit /MultiSource/Applications/oggenc/oggenc TEST-FAIL: cbe /MultiSource/Applications/oggenc/oggenc TEST-FAIL: jit /MultiSource/Applications/JM/ldecod/ldecod TEST-FAIL: llc /MultiSource/Applications/JM/lencod/lencod TEST-FAIL: jit /MultiSource/Applications/JM/lencod/lencod TEST-FAIL: cbe /MultiSource/Applications/JM/lencod/lencod TEST-FAIL: jit /MultiSource/Applications/obsequi/Obsequi TEST-FAIL: llc /MultiSource/Applications/kimwitu++/kc TEST-FA...

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