Guenther wrote:My guess is that the no popcount compile simply won't work with egbb...
Microsoft Windows [Version 10.0.15063]
(c) 2017 Microsoft Corporation. Alle Rechte vorbehalten.
C:\Users\Agando\Arena\Engines\Scorpio28>scorpio-nopop.exe
feature done=0
ht 8388608 X 16 = 128.0 MB
eht 1048576 X 8 = 8.0 MB
pht 32768 X 24 = 0.8 MB
processors [1]
new
EgbbProbe 4.1 by Daniel Shawul
145 egbbs loaded !
loading_time = 1s
they are loaded here!
BUT, is this a real no popcount hardware? - if my guess is true you can only simulate the behaviour on such hardware.
(my guess is that the egbbprobe code contains since a certain point popcount instructions)
Edit:
Also '145 egbb's loaded' doesn't sound like 3+4men only.
Please try to load only from a 3+4men folder (that's all what is available
from Daniels download for new egbb - this contains 70 egbbs)
Guenther wrote:BUT, is this a real no popcount hardware? - if my guess is true you can only simulate the behaviour on such hardware.
(my guess is that the egbbprobe code contains since a certain point popcount instructions)
I do not have PCs without popcount. But if earlier versions run on your pc,
did you try with the older egbb64 files? Mine are from 2006 and my oldest egbbdll is from 2009.
Just tested: the nonpopcount scorpio runs with these old egbb64 but only with egbbprobe 4.1, not with older Version 3.3.
But all older engines 2.4 - 2.7 run with these older egbbs and egbbdlls.
Guenther wrote:BUT, is this a real no popcount hardware? - if my guess is true you can only simulate the behaviour on such hardware.
(my guess is that the egbbprobe code contains since a certain point popcount instructions)
I do not have PCs without popcount. But if earlier versions run on your pc,
did you try with the older egbb64 files? Mine are from 2006 and my oldest egbbdll is from 2009.
Just tested: the nonpopcount scorpio runs with these old egbb64 but only with egbbprobe 4.1, not with older Version 3.3.
But all older engines 2.4 - 2.7 run with these older egbbs and egbbdlls.
Yes, as I said before, I tried all combinations after the suggestion of Daniel.
Newer versions also don't work with older egbb/egbb.dlls.
(of course those are all 64 bit and the older ones 32 bit)
It seems my assumption could be right!
32 bit versions from 2.7 and 2.75 (compiled by JA) work here for new and old egbb! (versions 3.3 and 4.1)
The problem are the 64 bit versions which don't work at all for all versions of egbb on my hardware.
It is 32 cores not cpus -- I should have named the flag -DMAX_CORES instead.
I think recompiling for 64 cores should make scorpio somewhat numa aware on linux systems -- no work done for Windows. Thread memory allocations are done on "first touch policy" that is all there is in Scorpio.
It was either a language problem or missinformation?
I always read that the egbbdllXYZ.dll should be renamed to egbbdll.dll, because of that I created extra folders for usage with the 64 bit versions and renamed the dll to plain egbbdll.dll.
Just right now I searched some older threads in the forum and found the decisive info! Sorry for the confusion, but I think it should be made more clear on the website/readme Daniel.
No problem at all and thanks for pointing out the problems! The egbbdll releases are kind of a mess and I should have provided a note on how to troubleshoot issues. Going through the old egbbdll/generator code/ now, I see many things that could cause problems for users -- such as endianess issues, case sensitive file naming on linux etc... I will work on those a bit and update the egbbdlls.
Daniel Shawul wrote:No problem at all and thanks for pointing out the problems! The egbbdll releases are kind of a mess and I should have provided a note on how to troubleshoot issues. Going through the old egbbdll/generator code/ now, I see many things that could cause problems for users -- such as endianess issues, case sensitive file naming on linux etc... I will work on those a bit and update the egbbdlls.
Daniel
Great.
And for others who have/had the same problem with Scorpio 64 bit versions and egbb, I see now I forgot to include the explicit solution :)
The egbbdll64.dll should not be renamed and must stay with that name!
