3 ms·
In C/C++ land the kind of ”Just try and see if it works” kind of development is super common in proprietary software. Leading to issues such as: Using volatile
by sharpneli 6y ago
In C/C++ land the kind of ”Just try and see if it works” kind of development is super common in proprietary software. Leading to issues such as:
Using volatile for threadsafe stuff. Arm has weaker memory model than X86 so it requires barriers. C++ standard threading lib handles this for you but not everyone uses it.
Memory alignment. Arm tends to be more critical of that. While it’s impossible for well formed C++ program to mess it up it’s quite common for people just go ”Hey it’s just a number” and go full yolo with it. Because hey, it works on their machine.
- pjscott 6y agoApple's recent 64-bit ARM processors now support unaligned memory access, so there's one porting problem out of the way: https://developer.arm.com/docs/den0024/latest/an-introduction-to-the-armv8-instruction-sets/the-armv8-instruction-sets/addressing https://developer.arm.com/docs/den0024/latest/an-introductio...