Clang is a compiler front end for the C, C++, Objective-C and Objective-C++ programming languages, as well as the OpenMP, OpenCL, RenderScript, CUDA and HIP frameworks. It uses the LLVM compiler infrastructure as its back end and has been part of the LLVM release cycle since LLVM 2.6.
It is designed to act as a drop-in replacement for the GNU Compiler Collection, supporting most of its compilation flags and unofficial language extensions. Its contributors include Apple, Microsoft, Google, ARM, Sony, Intel and Advanced Micro Devices. It is open-source software, with source code released under the University of Illinois/NCSA License, a permissive free software licence. Since v9.0.0, it was relicensed to the Apache License 2.0 with LLVM Exceptions.
The Clang project includes the Clang front end, a static analyzer, and several code analysis tools.


Starting in 2005, Apple Inc. made extensive use of LLVM in a number of commercial products, including the iOS SDK and Xcode 3.1.
One of the first uses of LLVM was an OpenGL code compiler for OS X that converts OpenGL calls into more fundamental calls for graphics processing units that do not support certain features. This allowed Apple to support OpenGL on computers using Intel Graphics Media Accelerator chipsets, increasing performance on those machines. For GPUs that support it, the code is compiled to fully exploit the underlying hardware, but on GMA machines, LLVM compiles the same OpenGL code into subroutines to ensure continued proper function.
LLVM was intended originally to use GCC's front end, but GCC turned out to cause some problems for developers of LLVM and at Apple. The GCC source code is a large and somewhat cumbersome system for developers to work with; as one long-time GCC developer put it referring to LLVM, "Trying to make the hippo dance is not really a lot of fun".
Apple software makes heavy use of Objective-C, but the Objective-C front-end in GCC is a low priority for GCC developers. Also, GCC does not integrate smoothly into Apple's integrated development environment. Finally, GCC is licensed under the terms of GNU General Public License version 3, which requires developers who distribute extensions for, or modified versions of, GCC to make their source code available, whereas LLVM has a BSD-like license which does not have such a requirement.
Apple chose to develop a new compiler front end from scratch, supporting C, Objective-C and C++. This "clang" project was open-sourced in July 2007.


Clang is intended to work on top of LLVM. The combination of Clang and LLVM provides most of the toolchain, to allow replacing the full GCC stack. Because it is built with a library-based design, like the rest of LLVM, Clang is easy to embed into other applications. This is one reason why most OpenCL implementations are built with Clang and LLVM.
One of Clang's main goals is to provide a library-based architecture, to allow the compiler to be more tightly tied to tools that interact with source code, such as an integrated development environment graphical user interface. In contrast, GCC is designed to work in a compile-link-debug workflow, and integrating it with other tools is not always easy. For instance, GCC uses a step called fold that is key to the overall compile process, which has the side effect of translating the code tree into a form that looks unlike the original source code. If an error is found during or after the fold step, it can be difficult to translate that back into one location in the original source. Also, vendors using the GCC stack within IDEs use separate tools to index the code, to provide features like syntax highlighting and autocomplete.
Clang is designed to retain more information during the compiling process than GCC, and to preserve the overall form of the original code. The goal of this is to make it easier to map errors back into the original source. The error reports offered by Clang are also aimed to be more detailed and specific, as well as machine-readable, so IDEs can index the output of the compiler during compiling. Modular design of the compiler can offer source code indexing, syntax checking, and other features normally associated with rapid application development systems. The parse tree is also more suitable for supporting automated code refactoring, as it directly represents the original source code.
Clang compiles only C-like languages, such as C, C++, Objective-C, Objective-C++, OpenCL, CUDA, and HIP. For other languages, like Ada, LLVM remains dependent on GCC or another compiler frontend. In many cases, Clang can be used or swapped out for GCC as needed, with no other effects on the toolchain as a whole. It supports most of the commonly used GCC options. A sub-project Flang by Nvidia and The Portland Group added Fortran support.

Performance and GCC compatibility

Clang is designed to be highly compatible with GCC. Clang's command-line interface is similar to and shares many flags and options with GCC. Clang implements many GNU language extensions and enables them by default. Clang implements many GCC compiler intrinsics purely for compatibility. For example, even though Clang implements atomic intrinsics which correspond exactly with C11 atomics, it also implements GCC's __sync_* intrinsics for compatibility with GCC and libstdc++. Clang also maintains ABI compatibility with GCC-generated object code. In practice Clang can often be used as a drop-in replacement for GCC.
Clang's developers aim to reduce memory footprint and increase compilation speed compared to competing compilers, such as GCC. In October 2007, they report that Clang compiled the Carbon libraries more than twice as fast as GCC, while using about one-sixth GCC's memory and disk space. However, as of 2011 this was not a typical result. As of mid-2014, Clang won more than a third of the benchmarks, with GCC winning most. As of 2014, performance of Clang-compiled programs lagged behind performance of the GCC-compiled program, sometimes by large factors, replicating earlier reports of slower performance.
More recent comparisons in November 2016 indicate that both compilers have evolved to increase their performance. As of GCC 4.8.2 versus clang 3.4, on a large harness of test files, GCC outperforms clang by approximately 17% on well-optimized source code. Test results are code-specific, and unoptimized C source code can reverse such differences. The two compilers now seem broadly comparable.

Status history

This table presents only significant steps and releases in Clang history.
11 July 2007Clang frontend released under open-source licence
25 February 2009Clang/LLVM can compile a working FreeBSD kernel.
16 March 2009Clang/LLVM can compile a working DragonFly BSD kernel.
23 October 2009Clang 1.0 released, with LLVM 2.6 for the first time.
December 2009Code generation for C and Objective-C reach production quality. Support for C++ and Objective-C++ still incomplete. Clang C++ can parse GCC 4.2 libstdc++ and generate working code for non-trivial programs, and can compile itself.
2 February 2010Clang self-hosting.
20 May 2010Clang latest version built the Boost C++ libraries successfully, and passed nearly all tests.
10 June 2010Clang/LLVM becomes integral part of FreeBSD, but default compiler is still GCC.
25 October 2010Clang/LLVM can compile a working modified Linux kernel.
January 2011Preliminary work completed to support the draft C++0x standard, with a few of the draft's new features supported in Clang development version.
10 February 2011Clang can compile a working HotSpot Java virtual machine.
19 January 2012Clang becomes an optional component in NetBSD cross-platform build system, but GCC is still default.
29 February 2012Clang 3.0 can rebuild 91.2% of the Debian archive.
29 February 2012Clang becomes default compiler in MINIX 3
12 May 2012Clang/LLVM announced to replace GCC in FreeBSD.
5 November 2012Clang becomes default compiler in FreeBSD 10.x.
18 February 2013Clang/LLVM can compile a working modified Android Linux Kernel for Nexus 7.
19 April 2013Clang is C++11 feature complete.
6 November 2013Clang is C++14 feature complete.
11 September 2014Clang 3.5 can rebuild 94.3% of the Debian archive. The percentage of failures has dropped by 1.2% per release since January 2013, mainly due to increased compatibility with GCC flags.
October 2016Clang becomes default compiler for Android.
13 March 2017Clang 4.0.0
26 July 2017Clang becomes default compiler in OpenBSD 6.2.
7 September 2017Clang 5.0.0
5 March 2018Clang is now used to build Google Chrome for Windows. Mozilla does the same change for Firefox in September same year.
8 March 2018Clang 6.0.0
19 September 2018Clang 7.0.0
20 March 2019Clang 8.0.0
19 September 2019Clang 9.0.0 with official RISC-V target support.
29 February 2020Clang becomes the only C compiler in the FreeBSD base system, with the removal of GCC.
24 March 2020Clang 10.0.0