Arm Compiler 6

Arm Compiler 6 is the production LLVM-based C/C++ compiler from Arm for Cortex-M, Cortex-R, and Cortex-A targets. It generates well-optimised code with Arm-specific optimisation passes layered on top of upstream LLVM. The same compiler engine powers the safety-qualified Arm Compiler for Embedded FuSa variant, see that product for the certification list and TUV SUD evidence package.

Safety qualification: see the FuSa variant

Arm Compiler 6 standard is the production compiler. For safety-critical projects (automotive ECUs, industrial controllers, railway signalling, medical devices) Arm publishes a separately licensed and qualified variant: Arm Compiler for Embedded FuSa. Per Arm’s published AC6 FuSa product page, AC6 FuSa is qualified to ISO 26262 (Automotive) ASIL D, IEC 61508 (Industrial) SIL 3, EN 50716 (Railways) SIL 4, and IEC 62304 (Medical) Class C. The standard AC6 product is not itself qualified, teams using AC6 in safety projects either move to AC6 FuSa or perform their own tool qualification with assessor sign-off.

Distribution and successor

Arm Compiler 6 is included in Keil MDK and Arm Development Studio, and is also available as a standalone product for integration into custom build systems and CI/CD pipelines. The successor for standard (non-FuSa) work is the LLVM-based Arm Toolchain for Embedded (ATfE): Arm’s long-term replacement for AC6, sold direct by Arm. AC6.22 LTS is the current maintenance branch for teams not yet ready to migrate, and remains the Arm-supported path for FuSa-qualified safety work today. For the AC6 FuSa → ATfE FuSa roadmap, talk to your Arm contact via GSAS. For the standard AC6 vs ATfE decision framework, see Arm Toolchain for Embedded vs Arm Compiler 6, Buyer’s Guide for Indian Cortex-M Teams.

Migrating from Arm Compiler 5 or GCC

Teams moving from Arm Compiler 5 (armcc) benefit from Arm Compiler 6’s LLVM-based architecture, which delivers measurably better code density and performance on Cortex-M and Cortex-R targets. Arm provides a migration guide covering pragma differences, inline assembly syntax changes, and linker script adjustments. For GCC-based projects, Arm Compiler 6 accepts most GNU extensions and GCC-compatible command-line options, which keeps the source-side transition manageable. Teams typically evaluate AC6 against their current toolchain on their own criteria, Arm-specific optimization passes, vendor support, and the availability of the separately licensed AC6 FuSa variant for safety projects are common reasons to move. In both cases, the compiler’s link-time optimization (LTO) and whole-program analysis passes often recover additional code size savings over the previous toolchain.

Why GSAS for Arm Compiler 6

GSAS provides Arm Compiler 6 licensing with local support for Indian engineering teams. Our services include migration consulting from legacy Arm Compiler 5 or GCC toolchains, safety qualification guidance aligned with your specific certification standard, and CI/CD integration for automated builds. Whether you need a standalone compiler license for a custom build system or are deploying Arm Compiler 6 as part of Keil MDK or Development Studio, GSAS handles procurement, license activation, and ongoing renewal management.