That SSE stuff is not maintained, you know.Crafty 19.15 is ready for download at http://home.earthlink.net/~bkhofmann/ should be the fastest Crafty yet....
Recommend:That SSE stuff is not maintained, you know.Crafty 19.15 is ready for download at http://home.earthlink.net/~bkhofmann/ should be the fastest Crafty yet....
I have tested these versions and they all work; in addition I run them on FICS and have done so for quite some time. I am a bit suprised by your comment stating it will break all over the place. Have you even tried any of these compiles and found problems? The SSE/SSE2 helps on Intel CPU speeds in my testing and there has never been a problem with them.Recommend:That SSE stuff is not maintained, you know.Crafty 19.15 is ready for download at http://home.earthlink.net/~bkhofmann/ should be the fastest Crafty yet....
do builds that do not have the extensions. Dr. Hyatt has not worked on that stuff for a very long time, and I would not be surprised if it were to break all over the place.
I would not be surprised if it is broken, since he has not used that pathway in a long time.I have tested these versions and they all work; in addition I run them on FICS and have done so for quite some time. I am a bit suprised by your comment stating it will break all over the place.Recommend:That SSE stuff is not maintained, you know.Crafty 19.15 is ready for download at http://home.earthlink.net/~bkhofmann/ should be the fastest Crafty yet....
do builds that do not have the extensions. Dr. Hyatt has not worked on that stuff for a very long time, and I would not be surprised if it were to break all over the place.
Have you even tried any of these compiles and found problems? The SSE/SSE2 helps on Intel CPU speeds in my testing and there has never been a problem with them.
Then maybe you need to contact the author of the program and let him know that he does not know how to compile his own program. If you look at the default make file for the icc-profile (this is what Hyatt uses for the ICC) it has the compile time option of -xN which mean optimize for the pentium 4. Guess what this does? It uses SSE/SSE2. So I guess if it is good enough for the author of the program to use should it not be offered to the other Crafty users.I would not be surprised if it is broken, since he has not used that pathway in a long time.I have tested these versions and they all work; in addition I run them on FICS and have done so for quite some time. I am a bit suprised by your comment stating it will break all over the place.Recommend:That SSE stuff is not maintained, you know.Crafty 19.15 is ready for download at http://home.earthlink.net/~bkhofmann/ should be the fastest Crafty yet....
do builds that do not have the extensions. Dr. Hyatt has not worked on that stuff for a very long time, and I would not be surprised if it were to break all over the place.
Have you even tried any of these compiles and found problems? The SSE/SSE2 helps on Intel CPU speeds in my testing and there has never been a problem with them.
I did search extension compiles before and I always had to do a lot of fiddling to ensure that things were not broken.
Do you run lint against the code base with your proposed flags defined?
That does not put SSE/SSE2 instructions into the program. It just chooses an instruction mix that is better for pentium 4. Which is neither here nor there. What I was trying to say is that all of these builds are questionable because they use aging code that is no longer tested. Not the comiler generated instructions, but the code patches for extensions.Then maybe you need to contact the author of the program and let him know that he does not know how to compile his own program. If you look at the default make file for the icc-profile (this is what Hyatt uses for the ICC) it has the compile time option of -xN which mean optimize for the pentium 4. Guess what this does? It uses SSE/SSE2. So I guess if it is good enough for the author of the program to use should it not be offered to the other Crafty users.I would not be surprised if it is broken, since he has not used that pathway in a long time.I have tested these versions and they all work; in addition I run them on FICS and have done so for quite some time. I am a bit suprised by your comment stating it will break all over the place.Recommend:That SSE stuff is not maintained, you know.Crafty 19.15 is ready for download at http://home.earthlink.net/~bkhofmann/ should be the fastest Crafty yet....
do builds that do not have the extensions. Dr. Hyatt has not worked on that stuff for a very long time, and I would not be surprised if it were to break all over the place.
Have you even tried any of these compiles and found problems? The SSE/SSE2 helps on Intel CPU speeds in my testing and there has never been a problem with them.
I did search extension compiles before and I always had to do a lot of fiddling to ensure that things were not broken.
Do you run lint against the code base with your proposed flags defined?
Not correct. When the -xN is specified the Vectoring component of the Intel compiler is enabled. This automaticly uses SIMD instructions (MMX SSE SSE2) as per the manual that comes with the Intel Compiler.That does not put SSE/SSE2 instructions into the program. It just chooses an instruction mix that is better for pentium 4.Then maybe you need to contact the author of the program and let him know that he does not know how to compile his own program. If you look at the default make file for the icc-profile (this is what Hyatt uses for the ICC) it has the compile time option of -xN which mean optimize for the pentium 4. Guess what this does? It uses SSE/SSE2. So I guess if it is good enough for the author of the program to use should it not be offered to the other Crafty users.I would not be surprised if it is broken, since he has not used that pathway in a long time.I have tested these versions and they all work; in addition I run them on FICS and have done so for quite some time. I am a bit suprised by your comment stating it will break all over the place.Recommend:That SSE stuff is not maintained, you know.Crafty 19.15 is ready for download at http://home.earthlink.net/~bkhofmann/ should be the fastest Crafty yet....
do builds that do not have the extensions. Dr. Hyatt has not worked on that stuff for a very long time, and I would not be surprised if it were to break all over the place.
Have you even tried any of these compiles and found problems? The SSE/SSE2 helps on Intel CPU speeds in my testing and there has never been a problem with them.
I did search extension compiles before and I always had to do a lot of fiddling to ensure that things were not broken.
Do you run lint against the code base with your proposed flags defined?
Which is neither here nor there. What I was trying to say is that all of these >builds are questionable because they use aging code that is no longer tested. >Not the comiler generated instructions, but the code patches for extensions.
Of course, I have not fiddled with extensions for a couple years. So maybe it is rock solid now. Of course, I use a less-tested extension too (DETECTDRAW) that could well introduce bugs.
I'm sure all this is confusing to the average Crafty user, at least it is to me. How to decide which version to use? Begging for help from Prof. Hyatt.Not correct. When the -xN is specified the Vectoring component of the Intel compiler is enabled. This automaticly uses SIMD instructions (MMX SSE SSE2) as per the manual that comes with the Intel Compiler.That does not put SSE/SSE2 instructions into the program. It just chooses an instruction mix that is better for pentium 4.Then maybe you need to contact the author of the program and let him know that he does not know how to compile his own program. If you look at the default make file for the icc-profile (this is what Hyatt uses for the ICC) it has the compile time option of -xN which mean optimize for the pentium 4. Guess what this does? It uses SSE/SSE2. So I guess if it is good enough for the author of the program to use should it not be offered to the other Crafty users.I would not be surprised if it is broken, since he has not used that pathway in a long time.I have tested these versions and they all work; in addition I run them on FICS and have done so for quite some time. I am a bit suprised by your comment stating it will break all over the place.Recommend:That SSE stuff is not maintained, you know.Crafty 19.15 is ready for download at http://home.earthlink.net/~bkhofmann/ should be the fastest Crafty yet....
do builds that do not have the extensions. Dr. Hyatt has not worked on that stuff for a very long time, and I would not be surprised if it were to break all over the place.
Have you even tried any of these compiles and found problems? The SSE/SSE2 helps on Intel CPU speeds in my testing and there has never been a problem with them.
I did search extension compiles before and I always had to do a lot of fiddling to ensure that things were not broken.
Do you run lint against the code base with your proposed flags defined?
Which is neither here nor there. What I was trying to say is that all of these >builds are questionable because they use aging code that is no longer tested. >Not the comiler generated instructions, but the code patches for extensions.
Of course, I have not fiddled with extensions for a couple years. So maybe it is rock solid now. Of course, I use a less-tested extension too (DETECTDRAW) that could well introduce bugs.
The only Crafty flag that is used in my builds are the FUTILITY. Here again if you look at the way the author of the program compiles his, he uses -DFUTILITY on the ICC system builds.
The author of the program stated he stopped using this option due to the slow down in performance. The cost was higher then the benefit.
The builds I have created are as close as possible to the builds that Hyatt uses himself. They are compiled for speed and the only mods I make are with this interest in mind and they do not effect the search, eval or other aspects of how the program was intended to play.
Dr Hyatt does not visit this site as far as I know. As to which one to use ... Well that's the great thing about choices ... Pick one or more then run it if you like it keep if you don't try another. The Crafty any X86 on my site should run with any x86 CPU and uses the same Crafty flags as Dr. Hyatt does with the version he runs on the ICC.I'm sure all this is confusing to the average Crafty user, at least it is to me. How to decide which version to use? Begging for help from Prof. Hyatt.Not correct. When the -xN is specified the Vectoring component of the Intel compiler is enabled. This automaticly uses SIMD instructions (MMX SSE SSE2) as per the manual that comes with the Intel Compiler.That does not put SSE/SSE2 instructions into the program. It just chooses an instruction mix that is better for pentium 4.Then maybe you need to contact the author of the program and let him know that he does not know how to compile his own program. If you look at the default make file for the icc-profile (this is what Hyatt uses for the ICC) it has the compile time option of -xN which mean optimize for the pentium 4. Guess what this does? It uses SSE/SSE2. So I guess if it is good enough for the author of the program to use should it not be offered to the other Crafty users.I would not be surprised if it is broken, since he has not used that pathway in a long time.I have tested these versions and they all work; in addition I run them on FICS and have done so for quite some time. I am a bit suprised by your comment stating it will break all over the place.Recommend:That SSE stuff is not maintained, you know.Crafty 19.15 is ready for download at http://home.earthlink.net/~bkhofmann/ should be the fastest Crafty yet....
do builds that do not have the extensions. Dr. Hyatt has not worked on that stuff for a very long time, and I would not be surprised if it were to break all over the place.
Have you even tried any of these compiles and found problems? The SSE/SSE2 helps on Intel CPU speeds in my testing and there has never been a problem with them.
I did search extension compiles before and I always had to do a lot of fiddling to ensure that things were not broken.
Do you run lint against the code base with your proposed flags defined?
Which is neither here nor there. What I was trying to say is that all of these >builds are questionable because they use aging code that is no longer tested. >Not the comiler generated instructions, but the code patches for extensions.
Of course, I have not fiddled with extensions for a couple years. So maybe it is rock solid now. Of course, I use a less-tested extension too (DETECTDRAW) that could well introduce bugs.
The only Crafty flag that is used in my builds are the FUTILITY. Here again if you look at the way the author of the program compiles his, he uses -DFUTILITY on the ICC system builds.
The author of the program stated he stopped using this option due to the slow down in performance. The cost was higher then the benefit.
The builds I have created are as close as possible to the builds that Hyatt uses himself. They are compiled for speed and the only mods I make are with this interest in mind and they do not effect the search, eval or other aspects of how the program was intended to play.
Dave
Hi BryanDr Hyatt does not visit this site as far as I know. As to which one to use ... Well that's the great thing about choices ... Pick one or more then run it if you like it keep if you don't try another. The Crafty any X86 on my site should run with any x86 CPU and uses the same Crafty flags as Dr. Hyatt does with the version he runs on the ICC.I'm sure all this is confusing to the average Crafty user, at least it is to me. How to decide which version to use? Begging for help from Prof. Hyatt.Not correct. When the -xN is specified the Vectoring component of the Intel compiler is enabled. This automaticly uses SIMD instructions (MMX SSE SSE2) as per the manual that comes with the Intel Compiler.That does not put SSE/SSE2 instructions into the program. It just chooses an instruction mix that is better for pentium 4.Then maybe you need to contact the author of the program and let him know that he does not know how to compile his own program. If you look at the default make file for the icc-profile (this is what Hyatt uses for the ICC) it has the compile time option of -xN which mean optimize for the pentium 4. Guess what this does? It uses SSE/SSE2. So I guess if it is good enough for the author of the program to use should it not be offered to the other Crafty users.I would not be surprised if it is broken, since he has not used that pathway in a long time.I have tested these versions and they all work; in addition I run them on FICS and have done so for quite some time. I am a bit suprised by your comment stating it will break all over the place.Recommend:That SSE stuff is not maintained, you know.Crafty 19.15 is ready for download at http://home.earthlink.net/~bkhofmann/ should be the fastest Crafty yet....
do builds that do not have the extensions. Dr. Hyatt has not worked on that stuff for a very long time, and I would not be surprised if it were to break all over the place.
Have you even tried any of these compiles and found problems? The SSE/SSE2 helps on Intel CPU speeds in my testing and there has never been a problem with them.
I did search extension compiles before and I always had to do a lot of fiddling to ensure that things were not broken.
Do you run lint against the code base with your proposed flags defined?
Which is neither here nor there. What I was trying to say is that all of these >builds are questionable because they use aging code that is no longer tested. >Not the comiler generated instructions, but the code patches for extensions.
Of course, I have not fiddled with extensions for a couple years. So maybe it is rock solid now. Of course, I use a less-tested extension too (DETECTDRAW) that could well introduce bugs.
The only Crafty flag that is used in my builds are the FUTILITY. Here again if you look at the way the author of the program compiles his, he uses -DFUTILITY on the ICC system builds.
The author of the program stated he stopped using this option due to the slow down in performance. The cost was higher then the benefit.
The builds I have created are as close as possible to the builds that Hyatt uses himself. They are compiled for speed and the only mods I make are with this interest in mind and they do not effect the search, eval or other aspects of how the program was intended to play.
Dave
Bryan
Maybe this will help. As far as the Crafty flag options my compiles use the exact same as Hyatt's (FUTILITY). Dan's compile does not use FUTILITY and he uses DETECTDRAW. The FUTILITY will speed things up but there is a chance that it may prune something out that is important. So there is a draw back to using the FUTILITY pruning. The DETECTDRAW has advantages in some positions but the draw back is it makes the eval slower. I have seen results of testing for the FUTILITY pruning posted on the CCC with 1000's of games played and it preformed better then the version without FUTILITY pruning. I have not seen any testing results with the DETECTDRAW so I can not say one way or another.Hi BryanDr Hyatt does not visit this site as far as I know. As to which one to use ... Well that's the great thing about choices ... Pick one or more then run it if you like it keep if you don't try another. The Crafty any X86 on my site should run with any x86 CPU and uses the same Crafty flags as Dr. Hyatt does with the version he runs on the ICC.I'm sure all this is confusing to the average Crafty user, at least it is to me. How to decide which version to use? Begging for help from Prof. Hyatt.Not correct. When the -xN is specified the Vectoring component of the Intel compiler is enabled. This automaticly uses SIMD instructions (MMX SSE SSE2) as per the manual that comes with the Intel Compiler.That does not put SSE/SSE2 instructions into the program. It just chooses an instruction mix that is better for pentium 4.Then maybe you need to contact the author of the program and let him know that he does not know how to compile his own program. If you look at the default make file for the icc-profile (this is what Hyatt uses for the ICC) it has the compile time option of -xN which mean optimize for the pentium 4. Guess what this does? It uses SSE/SSE2. So I guess if it is good enough for the author of the program to use should it not be offered to the other Crafty users.I would not be surprised if it is broken, since he has not used that pathway in a long time.I have tested these versions and they all work; in addition I run them on FICS and have done so for quite some time. I am a bit suprised by your comment stating it will break all over the place.Recommend:That SSE stuff is not maintained, you know.Crafty 19.15 is ready for download at http://home.earthlink.net/~bkhofmann/ should be the fastest Crafty yet....
do builds that do not have the extensions. Dr. Hyatt has not worked on that stuff for a very long time, and I would not be surprised if it were to break all over the place.
Have you even tried any of these compiles and found problems? The SSE/SSE2 helps on Intel CPU speeds in my testing and there has never been a problem with them.
I did search extension compiles before and I always had to do a lot of fiddling to ensure that things were not broken.
Do you run lint against the code base with your proposed flags defined?
Which is neither here nor there. What I was trying to say is that all of these >builds are questionable because they use aging code that is no longer tested. >Not the comiler generated instructions, but the code patches for extensions.
Of course, I have not fiddled with extensions for a couple years. So maybe it is rock solid now. Of course, I use a less-tested extension too (DETECTDRAW) that could well introduce bugs.
The only Crafty flag that is used in my builds are the FUTILITY. Here again if you look at the way the author of the program compiles his, he uses -DFUTILITY on the ICC system builds.
The author of the program stated he stopped using this option due to the slow down in performance. The cost was higher then the benefit.
The builds I have created are as close as possible to the builds that Hyatt uses himself. They are compiled for speed and the only mods I make are with this interest in mind and they do not effect the search, eval or other aspects of how the program was intended to play.
Dave
Bryan
Yes, choices are great, but ... with all this talk about "broken", i sure don't want to spend lots of time testing a version only to find out it was broken. I bench tested your version and Danns version. Your version is slightly better on NPS and slightly worse on time to ply. So bench results are a toss-up. So i must choose a version based on compile options, which i know nothing about, or spend lots of time testing both versions. By then, version 19.16 will probably be released.
Regards
Dave
If you compair different versions on your own computer it is probably easiest to just look at the time needed - the less time the better.For the non-techie users like myself, how should I read the bench tests results? I assume higher nodes per second is better. What about time to ply and other measurements? Are higher numbers better, or are lower better?
No easy answer here but for comparing the same version compiled differently the NPS is a sign of the speed. The Total time is also a factor in that it "x" maybe faster in time then "y" but "x" has a slower NPS. Normally you see a difference in a lower time when something in the seach or eval has been modified and a faster time is good. Also another item that will blur things is if one version was compiled with FUTILITY and another was not. The one compiled with FUTILITY will normall have a faster time due to the fact that less nodes were shearched due to prunning. The bench that is built into Crafty it is only looking at 6 positions from the BK test suite to a set depth and cares not about the correct solution so it is strictly a speed test. As for the SMP Time to PLY, all I can say here is the formua used to calucate it is (640.0 / (total_time_used / 100) and on faster system it is higher then slower. What Hyatt is acutally measuring with this I have no idea.For the non-techie users like myself, how should I read the bench tests results? I assume higher nodes per second is better. What about time to ply and other measurements? Are higher numbers better, or are lower better?
Return to Archive (Old Parsimony Forum)
Users browsing this forum: No registered users and 18 guests