The definitive guide to making software fail on ARM64
Even software, written in high-level cross-platform language with no assembly can fail multiple ways when ported to a different CPU architecture. Ignat Korchagin examines the issues Cloudflare encountered when porting its software stack to ARM64.
| Talk Title | The definitive guide to making software fail on ARM64 |
| Speakers | Ignat Korchagin (Cloudflare) |
| Conference | O’Reilly Velocity Conference |
| Conf Tag | Build systems that drive business |
| Location | Berlin, Germany |
| Date | November 5-7, 2019 |
| URL | Talk Page |
| Slides | Talk Slides |
| Video | |
Adopting a second CPU architecture into x86-only infrastructure can be a challenging task. Not only do you have to find the right hardware and learn how to properly provision it, but you also need to port the whole software stack, which was probably developed and improved for a number of years without having this second architecture in mind. And even though you might think that all the components of your stack are written in a cross-platform architecture-agnostic language (like Go or Java), there are still many ways they can fail on a secondary architecture after porting. Ignat Korchagin examines the issues Cloudflare encountered when porting its software stack to ARM64 and offers advice on how to avoid them when writing new code.
