TalkChess.com

Right, those idiots try hard to make each new version of gcc slower than the one before. Fortunately we have expert-testers who expose them. Good job Gabor!

Right, except that such super-instructions have to be useful in the first place. For large vector/matrix operations, it would be better to simply implement these in optimized C/C++/... (or even offload to a GPU) and expose them as functions to the (scripting) language (this is what Python does, bind...

The interpreter named "JVM 64Bit" is only about a factor 1.25 slower than compiled C-Code in terms of my chess engine. For me: This is quite surprising. You seem to misunderstand what an interpreter is. JVM compiles bytecode to machine code, it may interpret, but that would be horrendlously slow (j...

Of course, C is supposed to be faster than any other language, because it is translated easily 1:1 into machine code. umm, producing optimized machine code is incredibly hard, there's a reason why LLVM is 1M SLOC. An interpreted language is only 30% slower. I think, this is the result of a great ru...

Who told you Java should be faster than C? 30% slower is actually an excellent result for Java and I'm impressed and shocked (I can confirm ~31% on my machine as well - latest 64-bit hotspot vs 64-bit gcc O3). Hotspot is very good and from what I've seen it produces faster code than C# (.NET) I wond...

if you can use VS2019 and do a 32-bit build, you can try to enable ASAN (finally) to see if it detects any problems. 64-bit ASAN will come in the next version I think. One can never rule out compiler bugs, but these are rare. Also don't forget that in debug mode everything is pre/post-filled with sp...

nobody sane measures performance with optimizations disabled. you'd get totally unreliable results. nothing gets inlined, function prologue typically contains stack checks and fillers, nothing is cached in registers (everything spills), asserts are present in debug builds => typically debug builds r...

Removing history updates from Ethereal lost 760 elo at STC : http://chess.grantnet.us/viewTest/4369/ Obviously, Ethereal uses history counters for some pruning decisions, so the result is worse than having an engine that doesn't depend on history anywhere. I stand by "hundreds" in any case. Move or...

Because the type safety and the code analyzer are built into the language as integral parts, the compiler can tell you exactly what is wrong, where it is wrong, why it's wrong, AND how to fix it, along with a suggestion or code snippet on how to accomplish the fix. If you have never seen a Rust err...

History is worth hundreds of elo, a bug there costing 50 elo is nothing outlandish. That's a bold claim. I very much doubt that. Even if your "hundreds" would be 200, I still doubt that. Even if you use history for other decisions but move ordering. LMR alone is worth what, 100-200 max perhaps, sti...