Has there been a change in the flags for Crafty compilation? (E.g. are there new pruning techniques that have been added and which also require seeing macros?)For those without a compiler for windows and want an alternative to Dann's no futility Crafty compile you can go here http://home.earthlink.net/~bkhofmann/. I compiled Crafty 5 different ways with futility pruning as it seems Skinner is have problems compiling.
No change just add the /DFUTILITY to the compile time options. You can tell when a Crafty has been compiled without this by the total number of node searched in a benchmark. Below you can see your compile VS my compile.Has there been a change in the flags for Crafty compilation? (E.g. are there new pruning techniques that have been added and which also require seeing macros?)For those without a compiler for windows and want an alternative to Dann's no futility Crafty compile you can go here http://home.earthlink.net/~bkhofmann/. I compiled Crafty 5 different ways with futility pruning as it seems Skinner is have problems compiling.
I have tested your SSE compilation for my AMD Duron.For those without a compiler for windows and want an alternative to Dann's no futility Crafty compile you can go here http://home.earthlink.net/~bkhofmann/. I compiled Crafty 5 different ways with futility pruning as it seems Skinner is have problems compiling.
Bryan,No change just add the /DFUTILITY to the compile time options. You can tell when a Crafty has been compiled without this by the total number of node searched in a benchmark. Below you can see your compile VS my compile.Has there been a change in the flags for Crafty compilation? (E.g. are there new pruning techniques that have been added and which also require seeing macros?)For those without a compiler for windows and want an alternative to Dann's no futility Crafty compile you can go here http://home.earthlink.net/~bkhofmann/. I compiled Crafty 5 different ways with futility pruning as it seems Skinner is have problems compiling.
Crafty v19.14 (Dann Corbit Compile)
White(1): ben
Running benchmark. . .
......
Total nodes: 88943403
Raw nodes per second: 1170307
Total elapsed time: 76
SMP time-to-ply measurement: 8.421053
White(1): quit
Crafty v19.14 (My Compile)
White(1): ben
Running benchmark. . .
......
Total nodes: 78164348
Raw nodes per second: 1302739
Total elapsed time: 60
SMP time-to-ply measurement: 10.666667
I have tested your SSE compilation for my AMD Duron.For those without a compiler for windows and want an alternative to Dann's no futility Crafty compile you can go here http://home.earthlink.net/~bkhofmann/. I compiled Crafty 5 different ways with futility pruning as it seems Skinner is have problems compiling.
Under Arena it is not stable. It executs some ollegal action and is closed by Windows.
SL.
There are some issues with availlable Crafty 19.14 versions. Expect them to be fixed in 19.15 - for now it is probably a sensible idea for most to just skip 19.14 and wait for the imminent 19.15 release.I have tested your SSE compilation for my AMD Duron.For those without a compiler for windows and want an alternative to Dann's no futility Crafty compile you can go here http://home.earthlink.net/~bkhofmann/. I compiled Crafty 5 different ways with futility pruning as it seems Skinner is have problems compiling.
Under Arena it is not stable. It executs some ollegal action and is closed by Windows.
SL.
The Duron does not support SSE instructions, this is why it exits due to the program making these calls. You will have to use the Craftyx version from the web site. That compile does not have the SSE instructions.I have tested your SSE compilation for my AMD Duron.For those without a compiler for windows and want an alternative to Dann's no futility Crafty compile you can go here http://home.earthlink.net/~bkhofmann/. I compiled Crafty 5 different ways with futility pruning as it seems Skinner is have problems compiling.
Under Arena it is not stable. It executs some ollegal action and is closed by Windows.
SL.
Your system does not support SSE calls. You will have to use the Craftyx version from the web site. That compile does not have the SSE instructions. The SSE calls did not appear in AMDs until the XP versions.I have tested your SSE compilation for my AMD Duron.For those without a compiler for windows and want an alternative to Dann's no futility Crafty compile you can go here http://home.earthlink.net/~bkhofmann/. I compiled Crafty 5 different ways with futility pruning as it seems Skinner is have problems compiling.
Under Arena it is not stable. It executs some ollegal action and is closed by Windows.
SL.
I was a little to quick when I posted the first time and did recompile all of them as I noticed I did not remove the .obj files between the different version and wanted to ensure each one was fresh. If I do update them I will place a new date on the page.Bryan,No change just add the /DFUTILITY to the compile time options. You can tell when a Crafty has been compiled without this by the total number of node searched in a benchmark. Below you can see your compile VS my compile.Has there been a change in the flags for Crafty compilation? (E.g. are there new pruning techniques that have been added and which also require seeing macros?)For those without a compiler for windows and want an alternative to Dann's no futility Crafty compile you can go here http://home.earthlink.net/~bkhofmann/. I compiled Crafty 5 different ways with futility pruning as it seems Skinner is have problems compiling.
Crafty v19.14 (Dann Corbit Compile)
White(1): ben
Running benchmark. . .
......
Total nodes: 88943403
Raw nodes per second: 1170307
Total elapsed time: 76
SMP time-to-ply measurement: 8.421053
White(1): quit
Crafty v19.14 (My Compile)
White(1): ben
Running benchmark. . .
......
Total nodes: 78164348
Raw nodes per second: 1302739
Total elapsed time: 60
SMP time-to-ply measurement: 10.666667
Your compiled version of 19.14 works very well on Fritz8 gui. It is fast on the bench test and gets good results. I also notice that you make updates sporadically. May I suggest that you write down the time of each compilation so I can tell at a glance if I need an update?
It has nothing to do with the Crafty itself, their systems do no support SSE instructions and thus will not run. I made a compile for this on the web site that has no SSE instructions.There are some issues with availlable Crafty 19.14 versions. Expect them to be fixed in 19.15 - for now it is probably a sensible idea for most to just skip 19.14 and wait for the imminent 19.15 release.I have tested your SSE compilation for my AMD Duron.For those without a compiler for windows and want an alternative to Dann's no futility Crafty compile you can go here http://home.earthlink.net/~bkhofmann/. I compiled Crafty 5 different ways with futility pruning as it seems Skinner is have problems compiling.
Under Arena it is not stable. It executs some ollegal action and is closed by Windows.
SL.
PB
I run an amd xp2000+. Skinner's binaries usually don't do well on amd so it would not be a fair comparison to post. I do check them all and go with the one that has the best nodes per second on my machine. Posting speeds are not too meaningful because what counts is the speed on your own machine, not on someone else's machine.I was a little to quick when I posted the first time and did recompile all of them as I noticed I did not remove the .obj files between the different version and wanted to ensure each one was fresh. If I do update them I will place a new date on the page.Bryan,No change just add the /DFUTILITY to the compile time options. You can tell when a Crafty has been compiled without this by the total number of node searched in a benchmark. Below you can see your compile VS my compile.Has there been a change in the flags for Crafty compilation? (E.g. are there new pruning techniques that have been added and which also require seeing macros?)For those without a compiler for windows and want an alternative to Dann's no futility Crafty compile you can go here http://home.earthlink.net/~bkhofmann/. I compiled Crafty 5 different ways with futility pruning as it seems Skinner is have problems compiling.
Crafty v19.14 (Dann Corbit Compile)
White(1): ben
Running benchmark. . .
......
Total nodes: 88943403
Raw nodes per second: 1170307
Total elapsed time: 76
SMP time-to-ply measurement: 8.421053
White(1): quit
Crafty v19.14 (My Compile)
White(1): ben
Running benchmark. . .
......
Total nodes: 78164348
Raw nodes per second: 1302739
Total elapsed time: 60
SMP time-to-ply measurement: 10.666667
Your compiled version of 19.14 works very well on Fritz8 gui. It is fast on the bench test and gets good results. I also notice that you make updates sporadically. May I suggest that you write down the time of each compilation so I can tell at a glance if I need an update?
Do you run on a Intel system? If so can you compare my compile against Skinner's compile (http://crafty.webkikr.com) as my only intel system is a UNIX box.
I added a non-SSE version for the Athlon that you should be able to run with no problems.I have tested your SSE compilation for my AMD Duron.For those without a compiler for windows and want an alternative to Dann's no futility Crafty compile you can go here http://home.earthlink.net/~bkhofmann/. I compiled Crafty 5 different ways with futility pruning as it seems Skinner is have problems compiling.
Under Arena it is not stable. It executs some ollegal action and is closed by Windows.
SL.
Skinner compiles with the Intel compiler so yes it will be slower on AMD systems. In fact his fast compile is 12% slower then my slowest compile (Craftyx). I was just looking for a compairison on an Itell box.I run an amd xp2000+. Skinner's binaries usually don't do well on amd so it would not be a fair comparison to post. I do check them all and go with the one that has the best nodes per second on my machine. Posting speeds are not too meaningful because what counts is the speed on your own machine, not on someone else's machine.I was a little to quick when I posted the first time and did recompile all of them as I noticed I did not remove the .obj files between the different version and wanted to ensure each one was fresh. If I do update them I will place a new date on the page.Bryan,No change just add the /DFUTILITY to the compile time options. You can tell when a Crafty has been compiled without this by the total number of node searched in a benchmark. Below you can see your compile VS my compile.Has there been a change in the flags for Crafty compilation? (E.g. are there new pruning techniques that have been added and which also require seeing macros?)For those without a compiler for windows and want an alternative to Dann's no futility Crafty compile you can go here http://home.earthlink.net/~bkhofmann/. I compiled Crafty 5 different ways with futility pruning as it seems Skinner is have problems compiling.
Crafty v19.14 (Dann Corbit Compile)
White(1): ben
Running benchmark. . .
......
Total nodes: 88943403
Raw nodes per second: 1170307
Total elapsed time: 76
SMP time-to-ply measurement: 8.421053
White(1): quit
Crafty v19.14 (My Compile)
White(1): ben
Running benchmark. . .
......
Total nodes: 78164348
Raw nodes per second: 1302739
Total elapsed time: 60
SMP time-to-ply measurement: 10.666667
Your compiled version of 19.14 works very well on Fritz8 gui. It is fast on the bench test and gets good results. I also notice that you make updates sporadically. May I suggest that you write down the time of each compilation so I can tell at a glance if I need an update?
Do you run on a Intel system? If so can you compare my compile against Skinner's compile (http://crafty.webkikr.com) as my only intel system is a UNIX box.
Btw, I think that crafty 19.14 has a serious time management problem with fischer random (blitz) time. It does not use enough time at the beginning of the game so it loses too often and ends up with much time unused. 19.13 handles blitz time much, much better.
Sorry, my answer was somehow non-sequitur. But I seriously believe that it's better to wait for 19.15 in case time for engine testing is limitted.It has nothing to do with the Crafty itself, their systems do no support SSE instructions and thus will not run. I made a compile for this on the web site that has no SSE instructions.There are some issues with availlable Crafty 19.14 versions. Expect them to be fixed in 19.15 - for now it is probably a sensible idea for most to just skip 19.14 and wait for the imminent 19.15 release.I have tested your SSE compilation for my AMD Duron.For those without a compiler for windows and want an alternative to Dann's no futility Crafty compile you can go here http://home.earthlink.net/~bkhofmann/. I compiled Crafty 5 different ways with futility pruning as it seems Skinner is have problems compiling.
Under Arena it is not stable. It executs some ollegal action and is closed by Windows.
SL.
PB
Your system does not support SSE calls. You will have to use the Craftyx version from the web site. That compile does not have the SSE instructions. The SSE calls did not appear in AMDs until the XP versions.I have tested your SSE compilation for my AMD Duron.For those without a compiler for windows and want an alternative to Dann's no futility Crafty compile you can go here http://home.earthlink.net/~bkhofmann/. I compiled Crafty 5 different ways with futility pruning as it seems Skinner is have problems compiling.
Under Arena it is not stable. It executs some ollegal action and is closed by Windows.
SL.
Return to Archive (Old Parsimony Forum)
Users browsing this forum: Google [Bot] and 22 guests