Author: Bryan Hofmann
Date: 07:29:24 07/20/04
Go up one level in this thread
On July 20, 2004 at 03:51:07, Uri Blass wrote: >On July 19, 2004 at 20:56:02, Omar skulason wrote: > >>On July 19, 2004 at 19:22:19, Uri Blass wrote: >> >>>On July 19, 2004 at 18:35:04, Omar skulason wrote: >>> >>>>On July 19, 2004 at 16:48:29, Kurt Utzinger wrote: >>>> >>>>>As already mentioned earlier at >>>>>http://www.talkchess.com/forums/1/message.html?377725 >>>>>we are planning a long amateur tournament AT 2004 >>>>>and Crafty 19.15 WB under Arena will participate. >>>>>The games will be played on three identical Athlons 1.3 >>>>>and I am now wondering which versions (default or a compiled one) >>>>>we should use in this tourney. >>>>>Kind regards >>>>>Kurt >>>> >>>>Hi Kurt! >>>> >>>>I would pic Crafty v19.15 SE Ramat-Gan. It is the strongest in my computer. >>>>Slightly stronger than Crafty v19.15(DC) >>> >>> >>>What is the difference between them? >>> >>>Is there a difference in evaluation or search? >>> >>>If there is no difference then it is a waste of time to test them in tournaments >>>and you can simply pick the fastest version and use it. >>> >>>Uri >> >>Hi Uri! >>These 4 versions are not the same engine. The size differ for one thing. >>The BH beeing the smallest at 856 kb and the PS largest at 1.38 mb. >>Why don´t you test them together, it could be interesting. >> >> Ómar. > >The size of the exe tells me nothing. >It is possible to have different size of the exe because of different compiler. > >I asked if there is difference in the evaluation or the search and only the >programmer can answer me. > >If the only difference is that one is faster in nodes per seconds then it is >waste of time to play games between them. > >I do not have time to test them and I prefer to use time for testing movei. > >Uri Here is what I know about the different Crafties and may or may not be true; *Corbit Compile Compiler used = MS VC++ 6.0 ? NDEBUG = Remove DEBUG information from build WIN32 = There is no define in the default crafty code to use this _CONSOLE = Set the default link options and link libraries for console applications WINDOWS = There is no define in the default Crafty to use this. A Macro of _WINDOWS can be used to optimize programs for windows but this conflicts with the _CONSOLE macro. EGTB6 = Old Crafty compile option to allow for 6 man EGTBs. This is no longer used newer Crafty releases as the default uses 6 man tables if they are found. NT_i386 = Define Crafty build for use on a windows system. FAST = Compiles out some of the statistics gathering to slightly speed up the code. VC_INLINE_ASM = Use the Visual C assembly code DETECTDRAW = This enables experimental code that detects lots of the famous blocked-pawn positions as draws. It is much slower and perhaps slightly risky. EPD = Enable full EPD support in Crafty. USE_ASSEMBLY = Old Crafty compile option that is not used in the default crafty code. Mods made to Code = Initialize a few variables and also lengthen some paths to FILENAME_MAX size instead of 100 bytes. *Skinner Compile Compiler used = MS VC++ 6.0 & Intel C Compiler v 8.0 for Intel Builds and MS C/C++ Optimizing Compiler Version 13.10.3052 For AMD Builds WIN32 = There is no define in the default crafty code to use this _CONSOLE = Set the default link options and link libraries for console applications NT_i386 = Define Crafty build for use on a windows system. FAST = Compiles out some of the statistics gathering to slightly speed up the code. EGTB6 = Old Crafty compile option to allow for 6 man EGTBs. This is no longer used newer Crafty releases as the default uses 6 man tables if they are found. USE_ASSEMBLY = Old Crafty compile option that is not used in the default crafty code. VC_INLINE_ASM = Use the Visual C assembly code EPD = Enable full EPD support in Crafty. FUTILITY = enables "futility pruning" a forward-pruning algorithm Mods made to Code = Unknown * Hofmann Compile Compiler used = MS C/C++ Optimizing Compiler Version 13.10.3052 NT_i386 = Define Crafty build for use on a windows system. VC_INLINE_ASM = Use the Visual C assembly code FUTILITY = enables "futility pruning" a forward-pruning algorithm Mods made to Code = Removal of EPD & DGT code to produce a faster Crafty and other small changes. Nothing in the Eval, Search or anything that deals with chess playing is modified. These builds have two things in mind, speed and low memory usage. Crafty SE Byrne Compiler used = MS VC++ 6.0 & Intel C Compiler v 8.0 Flags = Unknown Mods made to Code = Several to include Eval and Search
This page took 0 seconds to execute
Last modified: Thu, 15 Apr 21 08:11:13 -0700
Current Computer Chess Club Forums at Talkchess. This site by Sean Mintz.