37 ms·
BTW x64 ans aarch64 have pretty different memory consistency models, so some performance-sensitive C++ code may either end up unnecessarily slow, or even surfac
by nine_k 4y ago
BTW x64 ans aarch64 have pretty different memory consistency models, so some performance-sensitive C++ code may either end up unnecessarily slow, or even surface a bug.
But this only applies to a very tiny amount of in-house code which hasn't been tested on aarch64 before.
I'd expect 99.9% of C++ code to just cross-compile and run without issues.
- liuliu 4y agoThe trick is on how to locate that 0.1% of C++ code ...
- nine_k 4y agoUsually stuff that implements advanced multithreading, concurrent thread-safe data structures, etc is pretty well isolated in a codebase, with spiky fences around it, and signs saying "You are not expected to understand this" [1] on the fences. [1]: http://9p.io/who/dmr/odd.html http://9p.io/who/dmr/odd.html
- isityouyesitsme 4y agoI'm not so sure. Maybe by literal line count. Maybe not by all targets in a large project. Literally every time in my life I've updated from version A of a compiler to version B of the same exact compiler, I had weeks of change sets required for getting the existing code to build under compiler B.