Files
mercury/extras/gator/evaluate.conf
Samrith Uong ad35cb9036 Changed the configuration files so that the program will work without
Estimated hours taken: 0.2

Changed the configuration files so that the program will work without
any additional configuration.

mercury/extras/gator/evaluate.conf:
       Instead of using the benchmark programs in the benchmarks
       directory (which the user might not have access to), use
       mercury/samples/hello.m as the benchmark program.

mercury/extras/gator/evolve.conf:
	Since the evaluate.conf file was changed so that there is
	only one benchmark program, we need to change the length of
	the first term.

mercury/extras/gator/gator.conf:
	In the previous revision, the hosts sophie, boadicea, surprise,
	lively and leopard were used.  Rather than use these hosts,
	which are only available to Mercury developers, use `hostname`
	instead.
2006-02-15 04:58:16 +00:00

33 lines
913 B
Plaintext

#
# num_progs: the number of programs used for benchmarking.
#
num_progs=1
#
# For each program, the following variables need to be defined.
#
# prog$i: the full path to the executable for the program (which may not
# yet be built). This may or may not be contained under
# "$benchmarks" (see gator.conf).
#
# clean$i: the command used to completely clean up the source directory.
#
# compile$i: the command used to compile the program. Note that you may
# assume there is a $flags shell variable which gives the
# optimization flags passed to the compiler.
#
# run$i: the command used to run the program.
#
prog1="$benchmarks"/hello
clean1="mmc --make hello.realclean; rm -rf Mercury"
compile1="mmc --make -O0 $flags hello"
run1="./hello"
#
# Some of the benchmarks can overflow the detstack. Set it high enough
# so that this won't happen.
#
MERCURY_OPTIONS="--detstack-size 32768"
export MERCURY_OPTIONS