4 ms·
This is what draws my attention more: > //FIXME: There's a threading issue in CryPhysics with ARM's weak memory ordering. https://github.com/CRYTEK/CRYENGINE/
by MauranKilom 6y ago
This is what draws my attention more:
> //FIXME: There's a threading issue in CryPhysics with ARM's weak memory ordering.
https://github.com/CRYTEK/CRYENGINE/blob/6c4f4df4a7a092300d630f8f89d2ebda39183c36/Code/CryEngine/CryCommon/CryPhysics/physinterface.h#L133 https://github.com/CRYTEK/CRYENGINE/blob/6c4f4df4a7a092300d6...
Translation: "We have race conditions in our C++, but x86 is lenient enough and current MSVC not aggressive enough to make it crash and burn constantly on our main platform."
Coincidentally, I finished Crysis 1 today. That involved the first four crashes I had with the game, three of which were in the final battle.
- 361994752 6y agoThis is not about race condition. Rather it is something more like why you need volatile keyword. https://stackoverflow.com/questions/72275/when-should-the-volatile-keyword-be-used-in-c https://stackoverflow.com/questions/72275/when-should-the-vo...
- MauranKilom 6y agoCan you elaborate? volatile and threading in C++ are orthogonal to each other. I don't understand why you consider a C# volatile discussion relevant when talking about C++ race conditions.
- ensiferum 6y agoVolatile in c++ has nothing to do with threading.