631.deepsjeng_s.flags 631.deepsjeng_s Flags
These are flags that appear in the benchmark sources, categorized as to whether they are portability candidates, mandatory, or forbidden.

]]>
The speed version of deepsjeng is compiled with BIG_MEMORY, and uses around 10x as much memory as the rate version. Having more memory allows more information to be stored about every position, notably if there are threats, or if there is only one good move. This information then causes some positions to be investigated deeper, which means it will take longer to reach the same search depth, but the result will be more accurate.

BIG_MEMORY is required when building the speed version of deepsjeng. It is set by object.pm, and must not be set in the user config file.

]]> SMALL_MEMORY causes allocation of around 700 MiB of memory. Compare to BIG_MEMORY.

The SMALL_MEMORY flag is required when building the rate version of deepsjeng. It is set by object.pm, and must not be set on the user config file.

]]> Do not set WIN32; use SPEC_WINDOWS instead (automatically supplied when compiling under 'runcpu') Do not set WIN64; use SPEC_WINDOWS instead (automatically supplied when compiling under 'runcpu') _MSC_VER disables some warnings. It is set by the compiler, and you should not set it from the command line. COPYPROTECTION causes information to be printed about move timing. It is not used in the SPEC version of deepsjeng. EVAL_DEBUG may be useful during a debug effort. It is not allowed for reportable runs. PAWN_EVAL_DEBUG may be useful during a debug effort. It is not allowed for reportable runs.