9 SSSSPPPPEEEECCCC BBBBeeeennnncccchhhhmmmmaaaarrrrkkkk SSSSppppeeeecccciiiiffffiiiiccccaaaattttiiiioooonnnnssss 9 072.sc 9 _1. _G_E_N_E_R_A_L _1._1. _C_l_a_s_s_i_f_i_c_a_t_i_o_n SC is a spreadsheet benchmark. It has some computations but is mostly screen handling. _1._2. _D_e_s_c_r_i_p_t_i_o_n SC performs standard operations expected of a spreadsheet. Cursor movements, data entry, data move- ments, file handling, row and column operations, opera- tions on ranges, numeric expessions and evaluations. _1._3. _S_o_u_r_c_e/_A_u_t_h_o_r The 'sc' code is public domain. (See the README and CHANGES files for more details). It has had many authors, one of the latest is Bob Bond of Sequent. _1._4. _V_e_r_s_i_o_n/_D_a_t_e The version is 6.1, date unknown. _1._5. _O_t_h_e_r _I_n_f_o_r_m_a_t_i_o_n The program has been run on a UNISYS 6000 and a SUN machine. Please email adv@unislc to report problems or to request information on the SPEC related issues that may arise. Bob Bond may be contacted for problems with the 'sc' program itself. 9 _2. _P_E_R_F_O_R_M_A_N_C_E _2._1. _M_e_t_r_i_c_s The program is run as a benchmark and the elapsed time (real) is used by SPEC. The time comes from /bin/time. _2._2. _E_l_a_p_s_e_d _T_i_m_e As above. The SPEC reference time is (to 3 sig. fig.) 4530 seconds. _2._3. _R_e_p_o_r_t_s The output of the benchmark is the final state of the spreadsheet. It is saved in a file for reference com- parison. 'sc' is run several times, with different inputs. _2._4. _A_d_d_i_t_i_o_n_a_l _P_e_r_f_o_r_m_a_n_c_e _C_o_n_s_i_d_e_r_a_t_i_o_n_s None. _3. _S_O_F_T_W_A_R_E _3._1. _L_a_n_g_u_a_g_e SC is a set of programs written in the C language. There are a number of files that come with 'sc' which are not needed to run it as a SPEC benchmark. These files have been moved to a directory called 'extrafiles' so that they are available for reference. _3._2. _O_p_e_r_a_t_i_n_g _S_y_s_t_e_m SC has run on a variety of UNIX systems including system V.2, V.3, BSD 4.2, 4.3, III (Xenix), and Venix. _3._3. _P_o_r_t_a_b_i_l_i_t_y Some of the documentation supplied with 'sc' addresses some portability issues. (See BSD_BUGS and VMS_NOTES). Your will need to pass some variables from the M.vendor file. Read the first part of the Makefile to determine what they are and what you settings should be. 9 9 _3._4. _V_e_c_t_o_r_i_z_a_b_i_l_i_t_y/_M_u_l_t_i-_P_r_o_c_e_s_s_o_r _I_s_s_u_e_s Non Vectorizabile. _3._5. _M_i_s_c_e_l_l_a_n_e_o_u_s _S_o_f_t_w_a_r_e termsize is a simple program that prints out the size of the terminal screen as understood by the curses package. For SPEC, termsize verifies that the screen size used by 072.sc is that required by the Run Rules. The Makefile builds termsize with exactly the same EXTRA_LIBS parameters that sc itself is built with. On systems that support both the older termcap-based curses and the newer terminfo-based curses, this assures that termsize will report the same screen size that sc will assume. _3._6. _K_n_o_w_n _B_u_g_s None. _3._7. _A_d_d_i_t_i_o_n_a_l _S_o_f_t_w_a_r_e _C_o_n_s_i_d_e_r_a_t_i_o_n_s None. _4. _H_A_R_D_W_A_R_E _4._1. _M_e_m_o_r_y No special requirments. _4._2. _D_i_s_k_s No special requirments. _4._3. _C_o_m_m_u_n_i_c_a_t_i_o_n The type of terminal device you have will greatly influ- ence the performance of this benchmark. A screen buffer type display will be faster than a 9600 baud terminal. The type of display should be a report item on the results. The terminal type should be like a VT100 (dev- ice or window), 24X80, performing all the standard screen attributes. _4._4. _S_p_e_c_i_a_l _H_a_r_d_w_a_r_e None. _4._5. _A_d_d_i_t_i_o_n_a_l _H_a_r_d_w_a_r_e _C_o_n_s_i_d_e_r_a_t_i_o_n_s None. 9 9 _5. _O_P_E_R_A_T_I_O_N_A_L _5._1. _D_i_s_k _S_p_a_c_e No disk requirments beyond the space required to hold the program source, executable image, input files and output files. This space is less than 1 megabyte. _5._2. _I_n_s_t_a_l_l_a_t_i_o_n Retrieve the 072.sc directory using tar. No special installation procedures required. _5._3. _E_x_e_c_u_t_i_o_n A sample command line to execute the program outside the Makefile is: sc test.file _5._4. _C_o_r_r_e_c_t_n_e_s_s _V_e_r_i_f_i_c_a_t_i_o_n The make file supplied will verify the final spreadsheet data with a reference file. A short version of the run (in time to run) can be made to verify that your machine can compile and run the benchmark. Use the following. make INMACH=short OUTMACH=short _5._5. _A_d_d_i_t_i_o_n_a_l _O_p_e_r_a_t_i_o_n_a_l _C_o_n_s_i_d_e_r_a_t_i_o_n_s If you are going to run it outside of the Makefile, there is a manual page supplied to document the commands to sc. (See sc.doc). _5._6. _S_a_m_p_l_e _R_u_n The make file will start sc, the input will come from a file, the cursor will move and the screen will be updated based on those inputs. The last command writes the spreadsheet data. That file is then compared for verification of the run. 9 9