Cyrano 0.3 32/64 bit Intel JA builds available

[Jim Ablett]

Cyrano v0.3 by Harald Johnsen
http://sites.estvideo.net/tipunch/cyrano/

32bit & 64bit Intel Compiler 10 p.g.o builds
http://www.zshare.net/download/71022382791fe4/

Jim.

[Tony Thomas]

I think you can read minds, I was going to post a compile request list soon. Here it is anyway.

Code: Select all

Hoichess
BBchess
Babychess
Cyrano

[Denis P. Mendoza]

Cyrano v0.3 by Harald Johnsen
http://sites.estvideo.net/tipunch/cyrano/

32bit & 64bit Intel Compiler 10 p.g.o builds
http://www.zshare.net/download/71022382791fe4/

Jim.

Thanks Master Jim. At least I know it's ICC friendly too. Cyrano-SRC is compatible with MSVC. I'm still babysitting my youngest daughter, so I'll try ICC32/64 bit builds later tomight. BTW Jim, it maybe necessary to rename line#60 of endgame.cpp from:

# define EGBB_NAME "egbbdll.dll"

to

# define EGBB_NAME "egbbdll64.dll"

and renaming the 64-bit probing dll at egbb folder to "egbbdll64.dll" as a simple solution when compiling the 64-bit engine. In this way, we exempt ourselves from creating another egbb folder. We can now mix the 64-bit and 32-bit egbb probing dll in the same folder so that any 32/64-bit bitbase enabled engine can access a common folder. But I'm not sure about a condition when two engines use the same probing dll at the same time (in this isolated case).Scorpio bitbase usage is becoming popular so this may fix some problems in the past. But I maybe wrong!

Just to inform the public, it uses the latest egmprobe v3.1 (egbbdll.dll) by Daniel Shawul as specifically called in the code. I made some epd endgame tests and it uses the 3-4-5 men bitbase pretty well. It works when this UCI option (as a UCI engine) is turned on and correct location of bitbase is set (ex. C:/egbb/ ). The default location from the code is not generic, F:/Chess/TB/egbbs_3_4/, so let us remember this. This is as far as I know.

Thanks Harald Johnsen Hjohnsen for this wonderful Gerbil derivative.

[Jim Ablett]

Hi Denis

just to inform the public, it uses the latest egmprobe v3.1 (egbbdll.dll) by Daniel Shawul as specifically called in the code.

I didn't bother with the egbb code because Harald Johnsen disabled egbb support in this release (says it's not working right at the moment.)
Quote from website..
'Cyrano 0.3 can use Scoripio bitbases but they are disabled by default, this needs more work to be usable (in a game).'

Jim.

[Zach Wegner]

But I'm not sure about a condition when two engines use the same probing dll at the same time (in this isolated case).Scorpio bitbase usage is becoming popular so this may fix some problems in the past. But I maybe wrong!

I don't know about DLL's, but for .so's on Unix, having multiple programs run them is the whole point, thus the name, shared object. It reduces executable size and memory footprints for keeping things like system functions only once and calling them from all programs.

[Denis P. Mendoza]

Hi Denis

just to inform the public, it uses the latest egmprobe v3.1 (egbbdll.dll) by Daniel Shawul as specifically called in the code.

I didn't bother with the egbb code because Harald Johnsen disabled egbb support in this release (says it's not working right at the moment.)
Quote from website..
'Cyrano 0.3 can use Scoripio bitbases but they are disabled by default, this needs more work to be usable (in a game).'

Jim.

Yes Jim, he mentioned that. By default, it is "false". But curiously, when I enabled it as a UCI-engine, it makes use of it. I just only tested it on some quick analysis, so my conclusions maybe wrong.

I tested w/ and w/o bitbase support with your compiles too using this sample positions taken from an endgame epd.

8/5p2/2k5/K7/8/1P6/8/8 b - - bm Kd5; id "UskiEG03";
8/8/4K3/4P2p/8/5k2/8/8 w - - bm Kf5; id "UskiEG04";
5k2/8/3K1Pp1/6P1/8/8/8/8 w - - bm f7; id "UskiEG05;

I'm sure you will see a difference

But there are probably still some tuning by Harald that's why he mentioned it. Thanks.

[Denis P. Mendoza]

But I'm not sure about a condition when two engines use the same probing dll at the same time (in this isolated case).Scorpio bitbase usage is becoming popular so this may fix some problems in the past. But I maybe wrong!

I don't know about DLL's, but for .so's on Unix, having multiple programs run them is the whole point, thus the name, shared object. It reduces executable size and memory footprints for keeping things like system functions only once and calling them from all programs.

You're right. Thanks for reminding me Zach... I should have read the WIKI first .