basil00
basil00
Using gcc extensions instead of x86 assembly is an improvement. But ideally we should make the code also portable to other compilers, e.g. msvc. I need to investigate the best...
Yep, not thread safe. It says so in the header documentation: ``` * - This function is NOT thread safe. For engines this function should only * be called once...
Thanks for the report. Just to clarify: is `LazyGull.exe` working on Windows 10? or not at all on Windows 10?
Yep, that's not good. Might be hard to track this down, and I don't work on this project anymore. Is there a way to reliably reproduce the crash?
Hmmmm, OK let me try a few tests on different machines.
I wasn't able to reproduce the crash so far. I can try some different machines next week.
I was never able to reproduce the bug. But I think it is likely because of the funky memory mapping idea I tried to port from Linux to Windows. Basically:...
I can't remember why, but my guess is that there was a linker bug. To "fix" the problem, it should not be too difficult to convert back to using global...
Yes, I think the current version assumes a CPU that supports `popcnt`. Only very old CPUs have this problem?