Migrating x86_64 workloads to aarch64
Introduction
Porting methodology
Porting analysis
Development environment
Application porting
Run and evaluate
Evaluating performance on Arm hardware (Optional)
Next Steps

  Log an issue

  Fork and edit

  Discuss on Discord

About this Learning Path

Skill level:  Advanced
Reading time:  30 min
Last updated:  13 Aug 2026
Skill level:
  Advanced
Reading time:
  30 min
Last updated:
  13 Aug 2026
Author:Kasper Mecklenburg, Arm
Arm IP:Cortex-A Neoverse
Tags: Performance and Architecture Linux GCC Arm Compiler for Linux Docker Neon
Author:
  • Kasper Mecklenburg, Arm
Arm IP:
Cortex-A Neoverse
Tags:
Performance and Architecture Linux GCC Arm Compiler for Linux Docker Neon

Who is this for?

This is an advanced topic for embedded software developers looking at migrating Linux workloads to aarch64.

What will you learn?

Upon completion of this Learning Path, you will be able to:

  • Understand software migration methodology
  • Use different Arm compilers and libraries
  • Port applications containing compiler intrinsics

Prerequisites

Before starting, you will need the following:

  • Introductory understanding of software containers
  • Knowledge about building workflows
  • Access to an aarch64 or x86_64 machine running Linux

Summary

AI-assisted

This summary was drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.

Close
?
You’ll migrate an x86_64 Linux Sobel-filter application to aarch64 through a structured porting workflow. First, you’ll create an aarch64 GCC container, adjust source and build options, replace x86_64 intrinsics with SIMD Everywhere (SIMDe), and compile with CMake. Then, you’ll run each implementation, compare execution times and images, and validate through emulation or remote Arm hardware.

Frequently asked questions

AI-assisted

These FAQs were drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.

Close
?
Which development environment should I use to build for `aarch64` on my `x86_64` host?
Use an aarch64 GCC development container on your x86_64 machine. Aim to match the original GCC version when possible, and run the build steps inside that container.
Where do I get the example application, and from which directory do I build?
Clone the GitHub repository and change into that directory. Follow the provided CMake commands to configure src into a build directory and then build from there.
How should I port the x86_64 SIMD intrinsics in the project?
Use SIMDe to replace the AVX intrinsics so the code compiles for aarch64. Make source and build option changes iteratively until the project compiles in the aarch64 container.
What result should I expect after I run the application?
The program prints execution times in microseconds for the non-SIMD, SIMD, and OpenCV implementations. It also opens four windows showing the original image and outputs from each implementation.
Do I need physical Arm hardware to follow this Learning Path?
No. You can run and validate the port using emulation or remote hardware. Physical Arm hardware isn’t required.
Next