search for: cint95

...= 0 call_trans2qfilepathinfo: TRANSACT2_QPATHINFO: level = 1004 call_trans2qfilepathinfo . (fnum = -1) level=1004 call=5 total_data=0 Transaction 27 of length 114 switch message SMBtrans2 (pid 2937) conn 0x8f6b038 call_trans2qfilepathinfo: TRANSACT2_QPATHINFO: level = 1004 call_trans2qfilepathinfo cint95-intel.mtw (fnum = -1) level=1004 call=5 total_data=0 Transaction 28 of length 114 switch message SMBtrans2 (pid 2937) conn 0x8f6b038 call_trans2qfilepathinfo: TRANSACT2_QPATHINFO: level = 1004 call_trans2qfilepathinfo cint95-intel.mtw (fnum = -1) level=1004 call=5 total_data=0 Transaction 29 of len...

Ok, I am trying to configure llvm to compile benchmarks as suggested by John, and after running configure, I get the following error while running make in the /test/Programs/External/SPEC ---- make[1]: Entering directory `/home/llvm/llvm/test/Programs/External/SPEC/CINT95' make[2]: Entering directory `/home/llvm/llvm/test/Programs/External/SPEC/CINT95/099.go' /home/llvm/llvm/tools/Debug/gccld -link-as-library -disable-opt -o Output/099.go.linked.rbc Not enough positional command line arguments specified! Must specify at least 1 positional arguments: See:...

...are disjoint; the LLVM build system may not work if one of them is a subdirectory of the other. 3) Can you send us the exact command line you used to run the configure script? Thanks, -- John T. > > ---- > make[1]: Entering directory > `/home/llvm/llvm/test/Programs/External/SPEC/CINT95' > make[2]: Entering directory > `/home/llvm/llvm/test/Programs/External/SPEC/CINT95/099.go' > /home/llvm/llvm/tools/Debug/gccld -link-as-library -disable-opt -o > Output/099.go.linked.rbc > Not enough positional command line arguments specified! > Must specify at least...

.../464.h264ref/464.h264ref 0.00% -0.30% 9.22% 0.72% SPEC/CINT2006/471.omnetpp/471.omnetpp 2.78% 1.92% 67.24% 3.92% SPEC/CINT2006/473.astar/473.astar 4.59% 6.61% 12.90% -0.87% SPEC/CINT2006/483.xalancbmk/483.xalancbmk 4.29% 0.00% 34.72% 0.00% SPEC/CINT95/099.go/099.go 0.00% -3.13% 46.93% 0.00% SPEC/CINT95/124.m88ksim/124.m88ksim 0.06% 0.00% 11.62% 50.00% SPEC/CINT95/126.gcc/126.gcc 0.24% 0.00% 36.70% 0.00% SPEC/CINT95/129.compress/129.compress 0.00% 0.00% 0.27% 0.00% SPE...

...ltiSource/Applications/hbd/hbd.compile 6.34% 1.7050 1.8131 0.0110 > MultiSource/Benchmarks/Prolangs-C/TimberWolfMC/timberwolfmc.compile 6.34% > 8.0582 8.5687 0.0539 > MultiSource/Benchmarks/MiBench/automotive-susan/automotive-susan.compile 6.33% > 1.0136 1.0778 0.0021 > External/SPEC/CINT95/134_perl/134_perl.compile 6.31% 6.3453 6.7457 0.0206 > External/SPEC/CFP2006/433_milc/433_milc.compile 6.29% 3.6706 3.9015 0.0293 > External/SPEC/CINT2006/462_libquantum/462_libquantum.compile 6.26% 0.9149 > 0.9722 0.0070 > MultiSource/Applications/spiff/spiff.compile 6.25% 0.8954 0.951...

...ns/hbd/hbd.compile 6.34% 1.7050 1.8131 0.0110 >> MultiSource/Benchmarks/Prolangs-C/TimberWolfMC/timberwolfmc.compile 6.34% >> 8.0582 8.5687 0.0539 >> MultiSource/Benchmarks/MiBench/automotive-susan/automotive-susan.compile 6.33% >> 1.0136 1.0778 0.0021 >> External/SPEC/CINT95/134_perl/134_perl.compile 6.31% 6.3453 6.7457 0.0206 >> External/SPEC/CFP2006/433_milc/433_milc.compile 6.29% 3.6706 3.9015 0.0293 >> External/SPEC/CINT2006/462_libquantum/462_libquantum.compile 6.26% 0.9149 >> 0.9722 0.0070 >> MultiSource/Applications/spiff/spiff.compile 6....

...ut/183.equake -3.2% MultiSource/Applications/hbd/Output/hbd -3.1% MultiSource/Applications/minisat/Output/minisat -3.0% MultiSource/Benchmarks/tramp3d-v4/Output/tramp3d-v4 -2.9% External/skidmarks10/Output/skidmarks -2.9% MultiSource/Benchmarks/ASCI_Purple/SMG2000/Output/smg2000 -2.8% External/SPEC/CINT95/132.ijpeg/Output/132.ijpeg -2.8% MultiSource/Benchmarks/MiBench/telecomm-gsm/Output/telecomm-gsm -2.8% MultiSource/Benchmarks/mediabench/gsm/toast/Output/toast -2.7% External/SPEC/CINT95/134.perl/Output/134.perl -2.6% MultiSource/Benchmarks/mediabench/jpeg/jpeg-6a/Output/cjpeg -2.6% MultiSource/App...

Does anyone know the "standard" commandline to compile and run spec95 benchmarks ? I found some scripts in llvm test suite (External/SPEC/CINT95), but I am not sure if they are the *default ref* configurations. <Some of them seem to use smaller problem sizes.> SPEC95 was retired many years ago, so few people around me know how to compile and run them. I am building from sourcefile without installation. so I expect commandlines li...

...still a remaining problem. thanks, --Long Chris Lattner wrote: > On Thu, 21 Jul 2005, Long Fei wrote: > >> Does anyone know the "standard" commandline to compile and run spec95 >> benchmarks ? >> >> I found some scripts in llvm test suite (External/SPEC/CINT95), but I >> am not sure if they are the *default ref* configurations. <Some of >> them seem to use smaller problem sizes.> SPEC95 was retired many >> years ago, so few people around me know how to compile and run them. >> >> I am building from sourcefile withou...

On Thu, 21 Jul 2005, Long Fei wrote: > Does anyone know the "standard" commandline to compile and run spec95 > benchmarks ? > > I found some scripts in llvm test suite (External/SPEC/CINT95), but I am not > sure if they are the *default ref* configurations. <Some of them seem to use > smaller problem sizes.> SPEC95 was retired many years ago, so few people > around me know how to compile and run them. > > I am building from sourcefile without installation. so I...

.... -Chris > Chris Lattner wrote: > >> On Thu, 21 Jul 2005, Long Fei wrote: >> >>> Does anyone know the "standard" commandline to compile and run spec95 >>> benchmarks ? >>> >>> I found some scripts in llvm test suite (External/SPEC/CINT95), but I am >>> not sure if they are the *default ref* configurations. <Some of them seem >>> to use smaller problem sizes.> SPEC95 was retired many years ago, so few >>> people around me know how to compile and run them. >>> >>> I am building f...

Hi John, I have attached my Makefile.config. I noticed that I did'nt have SRC_ROOT and OBJ_ROOT variables defined as such in my environment. But I noticed that this is defined in the Makefile.config by default to the same values. All the same, I tried defining both these variables in my .cshrc, but I still get the same error. The main directory for me is /home/llvm, and I have

Dear All, The i386 regressions: SPEC/CINT95/126.gcc/126.gcc Not too bad. :) -- John T. -- John T. Criswell Research Programmer University of Illinois at Urbana-Champaign "It's today!" said Piglet. "My favorite day," said Pooh.

...Makefile | |-- skidmarks10 | | `-- Makefile | `-- SPEC | |-- CFP2000 | | `-- Makefile | |-- CFP2006 | | `-- Makefile | |-- CFP95 | | `-- Makefile | |-- CINT2000 | | `-- Makefile | |-- CINT2006 | | `-- Makefile | |-- CINT95 | | `-- Makefile | |-- Makefile | |-- Makefile.spec | |-- Makefile.spec2000 | |-- Makefile.spec2006 | |-- Makefile.spec95 | `-- Makefile.spec.config |-- Makefile |-- Makefile.common |-- Makefile.config |-- Makefile.f2c |-- Makefile.nagfortran |-- Makefile...

...%2Flambda-0_1_3%2Flambda.compile=on> > 2.22% 0.8053 0.8232 0.0019 > MultiSource/Benchmarks/sim/sim.compile > <http://llvm.org/perf/db_default/simple/nts/380/graph?pset.0=on&test.MultiSource%2FBenchmarks%2Fsim%2Fsim.compile=on> > 2.20% 0.2948 0.3013 0.0003 > External/SPEC/CINT95/134_perl/134_perl.compile > <http://llvm.org/perf/db_default/simple/nts/380/graph?pset.0=on&test.External%2FSPEC%2FCINT95%2F134_perl%2F134_perl.compile=on> > 2.19% 6.2819 6.4196 0.0059 > External/SPEC/CINT2000/186_crafty/186_crafty.compile > <http://llvm.org/perf/db_default...

...google.com> wrote: > Does sinking these into the DAGCombine layer help? How much does it break? I tried disabling just the InstCombine transforms that hide shl instructions behind bitmasks. Even though DAGCombine has the same transforms, it causes some pretty bad regressions: External/SPEC/CINT95/147_vortex/147_vortex 0.294 0.322 +9.6% +40mB MultiSource/Benchmarks/Olden/tsp/tsp 0.680 0.748 +9.9% +41mB SingleSource/Benchmarks/Shootout-C++/except 0.116 0.128 +10.8% +45mB Si...

On Tue, Apr 17, 2012 at 12:23 AM, Jakob Stoklund Olesen <stoklund at 2pi.dk>wrote: > I am not sure how best to fix this. If possible, InstCombine's > canonicalization shouldn't hide arithmetic progressions behind bit masks. The entire concept of cleverly converting arithmetic to bit masks seems like the perfect domain for DAGCombine instead of InstCombine: 1) We know the

...config.status: executing External/SPEC/CINT2006/Makefile commands config.status: executing External/SPEC/CFP2000/Makefile commands config.status: executing External/SPEC/CINT2000/Makefile commands config.status: executing External/SPEC/CFP95/Makefile commands config.status: executing External/SPEC/CINT95/Makefile commands config.status: executing External/skidmarks10/Makefile commands config.status: executing MultiSource/Makefile commands config.status: executing MultiSource/Makefile.multisrc commands config.status: executing SingleSource/Makefile commands config.status: executing SingleSource/Make...

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".

Look at this silly function: $ cat small.c unsigned f(unsigned a, unsigned *p) { unsigned x = a/4; p[0] = x; p[1] = x+x; return p[1] - 2*p[0]; } GCC turns this into straightforward code and figures out the 0 return value: shrl $2, %edi movl %edi, (%rsi) addl %edi, %edi movl %edi, 4(%rsi) movl $0, %eax ret LLVM optimizes the code: $ clang -O -S -o- small.c -emit-llvm define i32