>>26
I haven't looked at the latest, but he did release executables with some custom debugging info. Executable itself seemed to have been optimized properly (debug mode by default uses little to no optimizations). It was probably be cause he used to use a mix of Intel's ICC and MSVC. I'd have to look at the latest executable to see what he's using now - if that path is an indication it would be gcc, but that would be a strange choice on Windows at least (it's fine, but optimization's worse than MSVC and ICC, and given that he cared enough to use ICC, why move to GCC?)