# Invocation command line: # ./bin/runspec -c cpu2006-rate-fp.m4000.s12u2-1027.cfg --reportable --rate fp # output_root was not used for this run ############################################################################ ############################################################################ ext = studio12u2-M4000-rate-fp-1027 parallel_setup = 16 parallel_setup_prefork = pbind -b $BIND $$ flagsurl000 = http://www.spec.org/cpu2006/flags/Oracle-Solaris-Studio12.2-SPARC.20101221.xml action = validate tune = all iterations = 1 # in a real run, would be 3 or more expand_notes = 1 ignore_errors = 1 log_line_width = 4090 # to avoid choking vi output_format = asc,cfgfile,csv,html mean_anyway = 1 minimize_rundirs = 1 minimize_builddirs = 1 preenv = 0 ####################### Processor usage ####################### # Note that the first instance of a "named section" occurs with # the copies line a little below. Therefore, any variables that # belong in the header section should be above this point. makeflags = -j32 # how many jobs specmake should spawn XJOBS = 32 # how many CPUs ipo can use (at link time) #preENV_OMP_NUM_THREADS = 32 #preENV_SUNW_MP_PROCBIND = true #preENV_SUNW_MP_THR_IDLE = SPIN command_add_redirect = 1 # useful with submit submit = echo 'pbind -b $BIND \$\$ >> pbind.out; $command' > dobmk; sh dobmk %ifndef %{OverRideCopies} # # To cause the command line to win for both base and peak, say: # # runspec --define OverRideCopies --rate n # # If you _don't_ say that, then the order of precedence is: # # named section (highest), about 6 lines down, peak for several benchmarks # command line # the line marked "header section default" just below # copies = 32 # header section default 436.cactusADM,481.wrf=peak=default=default: copies = 16 # fp that prefer otherwise 410.bwaves,437.leslie3d,450.soplex,470.lbm,482.sphinx3=peak=default=default: copies = 8 # fp that prefer otherwise # %endif default=default=default=default: ############################################################################ # In the bind statement below, the order of assignment is to work # from high to low, alternating LSBs, chips, cores, threads, from # highest to lowest. The order is derived from the 'prtdiag' # description of the machine. bind = <