Displaying 4 results from an estimated 4 matches for "spec_go".
2005 Jul 22
2
[LLVMdev] Need help on SPEC 95 "standard" commandlines
...($(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.c g2eye.c g2jlib2.c g2jos.c g2list.c g2reas.c g2s2.c
g2s3.c g2shp.c
and the running commandline:
./spec_go 50 9 2stone9.in
< are these correct ? >
This must be a shrinked problem size, since 2stone9.in is in the
training set, not the re...
2005 Jul 22
2
[LLVMdev] Need help on SPEC 95 "standard" commandlines
...he *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 like:
<gcc -Dflag1 -Dflag2 -O2 -o spec_go aaa.c bbb.c ... nnn.c -lm>
and then
<./spec_go param_1 param_2 ...>
For instance, in SPEC2000 175.vpr, we have:
1) gcc -DNDEBUG -DNO_GRAPHICS -O2 -o spec_vpr main.c util.c
read_netlist.c read_arch.c place.c route.c draw.c graphics.c stats.c
segment_stats.c rr_graph.c rr_graph2.c rr_grap...
2005 Jul 22
0
[LLVMdev] Need help on SPEC 95 "standard" commandlines
On Thu, 21 Jul 2005, Long Fei wrote:
> 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.c g2eye.c g2jlib2.c g2jos.c g2list.c g2reas.c g2s2.c g2s3.c g2shp.c
> and the running commandline:
> ./spec_go 50 9 2stone9.in
> < are these correct ? >
I believe that we only include test/train inputs for some programs.
&g...
2005 Jul 22
0
[LLVMdev] Need help on SPEC 95 "standard" commandlines
...ns. <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
> like:
> <gcc -Dflag1 -Dflag2 -O2 -o spec_go aaa.c bbb.c ... nnn.c -lm>
> and then
> <./spec_go param_1 param_2 ...>
>
> For instance, in SPEC2000 175.vpr, we have:
> 1) gcc -DNDEBUG -DNO_GRAPHICS -O2 -o spec_vpr main.c util.c read_netlist.c
> read_arch.c place.c route.c draw.c graphics.c stats.c segment_stats.c
&...