search for: cpu2000

...heers Gerolf On Sep 12, 2014, at 1:27 AM, Jiangning Liu <liujiangning1 at gmail.com> wrote: > Hi Hal, > > I run on SPEC2000 on cortex-a57(AArch64), and got the following results, > > (It is to measure run-time reduction, and negative is better performance) > > spec.cpu2000.ref.183_equake 33.77% > spec.cpu2000.ref.179_art 13.44% > spec.cpu2000.ref.256_bzip2 7.80% > spec.cpu2000.ref.186_crafty 3.69% > spec.cpu2000.ref.175_vpr 2.96% > spec.cpu2000.ref.176_gcc 1.77% > spec.cpu2000.ref.252_eon 1.77% > spec.cpu2000.ref.254_gap 1.19% > spec.cpu2000.r...

Hello everyone, One of Google's summer interns, George Burgess IV, created an implementation of the CFL pointer-aliasing analysis algorithm, and this has now been added to LLVM trunk. Now we should determine whether it is worthwhile adding this to the default optimization pipeline. For ease of testing, I've added the command line option -use-cfl-aa which will cause the CFL analysis to be

...l.com >>> wrote: >> >> >> >> Hi Hal, >> >> I run on SPEC2000 on cortex-a57(AArch64), and got the following >> results, >> >> (It is to measure run-time reduction, and negative is better >> performance) >> >> spec.cpu2000.ref.183_equake 33.77% >> spec.cpu2000.ref.179_art 13.44% >> spec.cpu2000.ref.256_bzip2 7.80% >> spec.cpu2000.ref.186_crafty 3.69% >> spec.cpu2000.ref.175_vpr 2.96% >> spec.cpu2000.ref.176_gcc 1.77% >> spec.cpu2000.ref.252_eon 1.77% >> spec.cpu2000.ref.254_g...

...AM, Jiangning Liu < liujiangning1 at gmail.com > > > wrote: > > > > Hi Hal, > > I run on SPEC2000 on cortex-a57(AArch64), and got the following > results, > > (It is to measure run-time reduction, and negative is better > performance) > > spec.cpu2000.ref.183_equake 33.77% > spec.cpu2000.ref.179_art 13.44% > spec.cpu2000.ref.256_bzip2 7.80% > spec.cpu2000.ref.186_crafty 3.69% > spec.cpu2000.ref.175_vpr 2.96% > spec.cpu2000.ref.176_gcc 1.77% > spec.cpu2000.ref.252_eon 1.77% > spec.cpu2000.ref.254_gap 1.19% > spec.cpu2000.r...

Hello LLVM-people, I've been trying (on and off) to compile the _full_ SPEC CPU2000 benchmark suite to LLVM bytecode. The biggest problem I'm facing is the Fortran benchmarks, for which some partial support is already available it seems (using f2c). Unfortunately the f2c compiler only allows the translation of Fortran-77 programs to C code (which is then compiled using...

Hi folks, I have been stumped on a compilation problem when I tried to build 176.gcc of SPEC CPU2000 with clang v 2.8 (trunk 427) on Linux and intel. First, I tried to compile with 'clang -std=c89 *.c -o gcc.clang' since the default C standard of Clang is c99 while that of gcc is c89. It reported this error: ./c-gperf.h:14:1: error: unknown type name 'inline' inline ^ ./c-gperf....

On Wed, 30 Aug 2006, Kenneth Hoste wrote: > I've been trying (on and off) to compile the _full_ SPEC CPU2000 benchmark > suite to LLVM bytecode. The biggest problem > I'm facing is the Fortran benchmarks, for which some partial support is > already available it seems (using f2c). ok. > Unfortunately the f2c compiler only allows the translation of Fortran-77 > programs to C code (wh...

On Thu, 31 Aug 2006, Kenneth Hoste wrote: >> $ grep F95 .../projects/llvm-test/Makefile.config > > -bash-3.00$ grep F95 projects/llvm-test/Makefile.config > # F95: Enable LLVM to run Fortran benchmarks without a Fortran front-end > USE_F95=1 > F95_DIR := > F95 := /work/NAG_f95/bin/f95 > F95_INC := /work/NAG_f95/lib > F95_LIB := /work/NAG_f95/lib > > Looks

On Thu, 31 Aug 2006, Kenneth Hoste wrote: > Bummer. I think I'll contact the NAG support for more info on this. Can you > show me the content of your Makefile.nagfortran? It is identical to yours. > Also, it is possible to tell make only to compile benchmark X? How can I > enforce this? Go into the directory for that benchmark, then run 'make' or whatever. -Chris --

On Thu, 31 Aug 2006, Kenneth Hoste wrote: >> It doesn't to me. If you set F95_DIR to /work/NAG_f95 things will >> probably work much better for you. > > No, that doesn't seem to be the problem. If I provide the additional > --with-f95 option with the correct directory to configure, > I still get the same errors (although it mentions /work/NAG_f95/lib/ >

Hi all, I find that SPEC cpu2k benchmark will always fail (9 of 10 times) for ia32 smp hvm guest with 4 vcpus. I used 4 users parameter to run cpu2k and assign 1G memory for the guest, but it will always fail when running 164.zip case and report warnings as the attachments. However, cpu2k could be run successfully in native linux and xenU guest with the same configuration. Anyone has ideas about

On 01/18/2011 06:38 PM, Bin Zeng wrote: > Hi folks, > > I have been stumped on a compilation problem when I tried to build > 176.gcc of SPEC CPU2000 with clang v 2.8 (trunk 427) on Linux and intel. > First, I tried to compile with 'clang -std=c89 *.c -o gcc.clang' since > the default C standard of Clang is c99 while that of gcc is c89. It > reported this error: > ./c-gperf.h:14:1: error: unknown type name 'inline' &g...

On 31 Aug 2006, at 19:13, Chris Lattner wrote: > On Thu, 31 Aug 2006, Kenneth Hoste wrote: > >> When I adjust the settings in Makefile.nagfortran as follows, I'm >> able to get bytecode file for lucas, galgel and facerec, but make >> still quits with an error (after generating >> bytecode files for 7 (out of 26) benchmarks. >> >> Also, the file

...e wrote: > >> >>> Also, it is possible to tell make only to compile benchmark X? How >>> can I >>> enforce this? >> >> Go into the directory for that benchmark, then run 'make' or >> whatever. > I tried tom compile each of the SPEC CPU2000 benchmarks using the make command is each respective subdirectory of llvm-test/External/SPEC. My setup: LLVM-1.8 with the gcc4 frontend (gcc-4.0.1). The NAG f95 compiler is v5.1(216). My platform is Fedora Core 4 on a Intel Pentium 4. I was confronted with 6 different errors for the various...

...te: >> I use NAG with llvm-gcc4. What sort of errors do you get? Did you >> configure llvm-test with the appropriate flags to find it? > Yes, I did. llvm-test is configured as follows: (in /work/LLVM/1.8/ > llvm/project/llvm-test): > ./configure --with-spec2000=/work/SPEC_CPU2000_1.3_src/benchspec -- > without-f2c --with-f95-bin=/work/NAG_f95/bin --with-f95-lib=/work/NAG_f95/lib > --with-f95-inc=/work/NAG_f95/lib --with-llvmsrc=/work/LLVM/1.8/llvm > --with-llvmobj=/work/LLVM/1.8/llvm What does this print? $ grep F95 .../projects/llvm-test/Makefile.config ? &gt...

On 31 Aug 2006, at 07:58, Chris Lattner wrote: > On Thu, 31 Aug 2006, Kenneth Hoste wrote: >>> $ grep F95 .../projects/llvm-test/Makefile.config >> >> -bash-3.00$ grep F95 projects/llvm-test/Makefile.config >> # F95: Enable LLVM to run Fortran benchmarks without a Fortran >> front-end >> USE_F95=1 >> F95_DIR := >> F95 :=

...e NAG with llvm-gcc4. What sort of errors do you get? Did >>> you configure llvm-test with the appropriate flags to find it? >> Yes, I did. llvm-test is configured as follows: (in /work/LLVM/ >> 1.8/ llvm/project/llvm-test): >> ./configure --with-spec2000=/work/SPEC_CPU2000_1.3_src/benchspec >> -- without-f2c --with-f95-bin=/work/NAG_f95/bin --with-f95-lib=/ >> work/NAG_f95/lib --with-f95-inc=/work/NAG_f95/lib --with-llvmsrc=/ >> work/LLVM/1.8/llvm --with-llvmobj=/work/LLVM/1.8/llvm > > What does this print? > > $ grep F95 .../project...

...f and Renato's concerns, and the impact/dependence upon link-time tool should be clarified before disabling this pass. On the other hand, actually the test on our hardware shows disabling this pass without LTO considered, some spec benchmarks would have big regressions, (positive is bad) spec.cpu2000.ref.253_perlbmk 3.27% spec.cpu2000.ref.254_gap 3.18% although I do see some improvements like below, (negative is good) spec.cpu2006.ref.400_perlbench -1.90% spec.cpu2006.ref.471_omnetpp -1.64% spec.cpu2006.ref.482_sphinx3 -1.03% Thanks, -Jiangning 2015-02-26 20:09 GMT+08:00 Renato Golin <r...

...mark X? How >> can I >> enforce this? > > Go into the directory for that benchmark, then run 'make' or whatever. OK, I seem to be getting closer to the problem... When compiling a single benchmark, I noticed the following... /work/NAG_f95/bin/f95 -w -S -O2 /work/SPEC_CPU2000_1.3_src/benchspec/ CFP2000/168.wupwise/src/dcabs1.f -o dcabs1.c -dusty -dcfuns Evaluation trial version of NAGWare Fortran 95 Release 5.1(216) /home/kehoste/work/LLVM/1.8/llvm-gcc4-1.8-x86-linux/bin/llvm-gcc - DSPEC_CPU2000 -I/home/kehoste/work/LLVM/1.8/llvm/projects/llvm-test/ External/SPEC/CFP...

...mp_6794_156' > > These also include SPECint benchmarks, so again, this has nothing > todo with f95. > >> *** perlbmk syntax error >> >> Compiling the perlbmk benchmark produces a syntax error. This may be >> a GCC4 problem. >> >> <path>/SPEC_CPU2000_1.3_src/benchspec/CINT2000/253.perlbmk/src/ >> nt_perlmain.c:80: error: syntax error before ‘int’ >> >> (among others) >> >> This specific line of code is: >> >> DllExport int RunPerl(int argc, char **argv, char **env, void *ios); >> >> which do...