LOCALDEFS
From BenchIT-Wiki
What are LOCALDEFS
The folder ./LOCALDEFS holds the machine-specific data. So whenever somewhat or somewho is refering to the configuration of your machine in a benchit-centric way he/she or it is talking about your LOCALDEFS. Each machine generates 3 files as its set of definitions. These files are named after the hostname of the machine. They are created by the ./tools/FIRSTTIME script and can be changed or extended by the user.
LOCALDEFS consist of 3 files named after the HOSTNAME of the machine:
- HOSTNAME
- minimal information needed to run BenchIT
- Section 1 Architectural Information
- some information about the hardware needed for naming the result files
- amount of memory that benchit is allowed to use
- timelimit for the execution
- Section 2 Library Linking Options
- Section 3 Compiler Options
- here you can specify what compilers and flags to use for the different supported languages
- our configuration script that should be used for the first setup only tests for some common compilers if you are using compilers provided by your hardware vendor it is very likely that you have to modify this section
- Section 4 Additional Options
- what does not fit elsewhere
- Section 1 Architectural Information
- The values in this file are used by the ./COMPILE.SH and ./RUN.SH scripts. They are made available as environment variables during the measurements and can be accessed by the BenchIT-Core and the BenchIT-Kernels using the bi_getenv() function from the Interface.
- minimal information needed to run BenchIT
- HOSTNAME_input_architekture
- HOSTNAME_input_display
- This file contains information about how the results should be plotted with gnuplot.
Presets
Please post a fully filled out set of your LOCALDEFS in form of a tar.bz2 or tar.gz
Some Localdefs can also be found in the CVS tree.
