search for: stdout_filenam

...gcc makefile, for example, you'll see: RUN_OPTIONS := -quiet -funroll-loops -fforce-mem -fcse-follow-jumps -fcse-skip-blocks -fexpensive-optimizati ons -fstrength-reduce -fpeephole -fschedule-insns -finline-functions -fschedule-insns2 -O -o - ifeq ($(RUN_TYPE),test) STDIN_FILENAME = cccp.i STDOUT_FILENAME = cccp.s else STDIN_FILENAME = amptjp.i STDOUT_FILENAME = amptjp.s endif Note that llvm-test compiles the benchmarks a file at a time (with -c), not all at once. -Chris -- http://nondot.org/sabre/ http://llvm.org/

Some of the run commandlines don't seem to be the *default ref* configuration. For instance, in 099.go, what's in the script is: LEVEL = ../../../.. BM=099.go ifeq ($(RUN_TYPE),test) STDIN_FILENAME = /dev/null STDOUT_FILENAME = null.out RUN_OPTIONS = 40 19 else STDIN_FILENAME = 2stone9.in STDOUT_FILENAME = 2stone9.out RUN_OPTIONS = 50 9 endif include ../../Makefile.spec95 Makefile (END) which suggests the compiling command: gcc -DSPEC_CPU95 -O2 -o spec_go g2.c g22.c g23.c g25.c g26.c g27a.c g27b.c g28.c g29....

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

...iet -funroll-loops -fforce-mem -fcse-follow-jumps >> -fcse-skip-blocks -fexpensive-optimizati >> ons -fstrength-reduce -fpeephole -fschedule-insns -finline-functions >> -fschedule-insns2 -O -o - >> >> ifeq ($(RUN_TYPE),test) >> STDIN_FILENAME = cccp.i >> STDOUT_FILENAME = cccp.s >> else >> STDIN_FILENAME = amptjp.i >> STDOUT_FILENAME = amptjp.s >> endif >> >> Note that llvm-test compiles the benchmarks a file at a time (with -c), not >> all at once. >> >> -Chris >> > > _________________________...

On Sun, 4 Sep 2005, Tanu Sharma wrote: > > I have a doubt. > > This is an excerpt of the raw report I get after running Spec benchmarks > through llvm-test.I am trying to calculate the program execution > time.Does the output result in bold corresponds to "lli time" in > Makefile.spec ? I am not interested in llc, jit or cbe.I simply need the > normal

I have a doubt. This is an excerpt of the raw report I get after running Spec benchmarks through llvm-test.I am trying to calculate the program execution time.Does the output result in bold corresponds to "lli time" in Makefile.spec ? I am not interested in llc, jit or cbe.I simply need the normal bytecode and native code execution times after running my pass over them.I have modified