deleualex

Hi All! I'm relatively new to the project and just started to get familiar with the code. It's a great way to keep in shape. I just have one curiosity: I see in the code in several places this COMPILER_FENCE macro that uses the deprecated intrinsic function "ReadWriteBarrier". According to MS Docs: The _ReadBarrier, _WriteBarrier, and _ReadWriteBarrier compiler intrinsics and the MemoryBarrier macro are all deprecated and should not be used. For inter-thread communication, use mechanisms such as atomic_thread_fence and std::atomic<T>, which are defined in the C++ Standard Library. For hardware access, use the /volatile:iso compiler option together with the volatile keyword. Do you guys see any risk in continuing to use this? It's used quite often in the code, and it's a quite sensitive matter I recon (memory and compiler optimization). Thanks, Alex