4 ms·
Elsewhere in the documentation[0] Apple explicitly calls out that code that relies on x86 memory ordering will need to be modified to contain explicit barriers.
by AndrewStephens 6y ago
Elsewhere in the documentation[0] Apple explicitly calls out that code that relies on x86 memory ordering will need to be modified to contain explicit barriers. All sensible code will do this already.
[0] https://developer.apple.com/documentation/apple_silicon/addressing_architectural_differences_in_your_macos_code https://developer.apple.com/documentation/apple_silicon/addr...
- gpderetta 6y agoSure, for source translation that's sorta fine (although I wouldn't want to be the one debugging it). The issue is binary translation, there is really no such a thing as a acquire or release barrier on x86.