Clang

ClangFile:Clang 21.1.7 version and compile information screenshot.webp

Screenshot of Clang 21.1.7 version information and verbose compile information, along with the compiled program

Original author(s)| Chris Lattner
Developer(s)| LLVM Developer Group
Initial release| September 26, 2007; 18 years ago (2007-09-26)[1]
Written in| C++
Operating system| Unix-like
Platform| AArch64, ARMv7, IA-32, x86-64, ppc64le[2]
Type| Compiler front end
License| Apache 2.0 with LLVM Exceptions[3][4]
Website| clang.llvm.org

Clang (/ˈklæŋ/)[5] is a compiler front end for the programming languages C, C++, Objective-C, Objective-C++, and the software frameworks OpenMP,[6] OpenCL, RenderScript, CUDA, SYCL, and HIP.[7] It acts as a drop-in replacement for the GNU Compiler Collection (GCC), supporting most of its compiling flags and unofficial language extensions.[8][9] It includes a static analyzer, and several code analysis tools.[10]

Clang operates in tandem with the LLVM compiler back end and has been a subproject of LLVM 2.6 and later.[11] As with LLVM, it is free and open-source software under the Apache 2.0 software license.[3][4] Its contributors include Apple, IBM, Microsoft, Google, ARM, Sony, Intel and AMD.

Clang 17 has full support for all published C++ standards up to C++17, implements most features of C++20, and has initial support for the C++23 standard.[12] Since v16.0.0, Clang compiles C++ using the GNU++17 dialect by default, which includes features from the C++17 standard and conforming GNU extensions.[13]

## Contents

* 1 Background
* 2 Design
* 2.1 Flang - Fortran
* 3 Performance and GCC compatibility
* 4 Interface
* 5 Status history
* 6 See also
* 7 References
* 8 External links

## Background

In 2005, Apple Inc. made extensive use of LLVM in several commercial products,[14] including the iOS SDK and Xcode 3.1. An OpenGL code compiler for OS X that converts OpenGL calls into more fundamental calls for graphics processing units (GPU) that do not support certain features, was one of the first uses of LLVM. This enabled Apple to support OpenGL on computers using Intel GMA chipsets, increasing performance on those machines.[15]

The LLVM project originally intended to use GCC's front end. The GCC source code, however, is large and somewhat cumbersome; as one long-time GCC developer put it referring to LLVM, "Trying to make the hippo dance is not really a lot of fun".[16] Besides, Apple software uses Objective-C, which is a low priority for GCC developers. As such, GCC does not integrate smoothly into Apple's integrated development environment.[17] Finally, GCC's license agreement, the GNU General Public License (GPL) version 3, requires developers who distribute extensions or modified versions of GCC to make their source code available, but LLVM's permissive software license doesn't require this.[3][4]

For these reasons, Apple developed Clang, a new compiler front end which supports C, Objective-C and C++.[17] In July 2007, the project received the approval for becoming open-source.[18]

## Design

Clang works in tandem with LLVM.[19] The combination of Clang and LLVM provides most of the toolchain for replacing the GCC stack. One of Clang's main goals is to provide a library-based architecture,[20] so that the compiler could interoperate with other tools that interact with source code, such as integrated development environments (IDE). In contrast, GCC works in a compile-link-debug workflow; 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. Besides, vendors using the GCC stack within IDEs must use separate tools to index the code, to provide features like syntax highlighting and intelligent code completion.

Clang retains more information during the compiling process than GCC, and preserves the overall form of the original code, making it easier to map errors back into the original source. Clang's error reports are more detailed, specific, and machine-readable, so IDEs can index the compiler's output. 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, and Objective-C++. In many cases, Clang can replace GCC as needed, with no other effects on the toolchain as a whole. It supports most of the commonly used GCC options. A Fortran project, Flang was in-progress in 2022. However, for other languages, such as Ada, LLVM remains dependent on GCC or another compiler front end.

### Flang - Fortran

The Flang project by Nvidia and The Portland Group adds Fortran support.[21] Flang is LLVM's Fortran frontend. It is often referred to as "LLVM Flang" to differentiate itself from "Classic Flang" – these are two separate and independent Fortran compilers. "LLVM Flang" is under active development. Development versions of Flang were in progress as of October 2023[update] and could be downloaded from the LLVM Project.[22]

## Performance and GCC compatibility

Clang compiling htop

Clang is compatible with GCC.[9] Its command-line interface shares many of GCC's flags and options. Clang implements many GNU language extensions and compiler intrinsics, some of which are 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 the C++ Standard Library (libstdc++). Clang also maintains application binary interface (ABI) compatibility with GCC-generated object code. In practice, Clang is a drop-in replacement for GCC.[23]

Clang's developers aim to reduce memory footprint and increase compiling speed compared to other 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.[24] By 2011, Clang seemed to retain this advantage in compiler performance.[25][26] As of mid-2014, Clang still consistently compiles faster than GCC in a mixed compile time and program performance benchmark.[27] However, by 2019, Clang is significantly slower at compiling the Linux Kernel than GCC while remaining slightly faster at compiling LLVM.[28]

While Clang has historically been faster than GCC at compiling, the output quality has lagged behind. As of 2014, performance of Clang-compiled programs lagged behind performance of the GCC-compiled program, sometimes by large factors (up to 5.5x),[27] replicating earlier reports of slower performance.[25] Both compilers have evolved to increase their performance since then, with the gap narrowing:

* Comparisons in November 2016 between GCC 4.8.2 versus clang 3.4, on a large harness of test files shows that 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 thus seem broadly comparable.[29] * Comparisons in 2019 on Intel Ice Lake has shown that programs generated by Clang 10 has achieved 96% of the performance of GCC 10 over 41 different benchmarks (while winning 22 and losing 19 out of them).[28]
* Another comparison conducted in 2023 revealed that programs compiled using Clang now match the performance of those compiled with GCC. On average, Clang 16 surpasses GCC 13 by 6%.[30]

## Interface

`libclang` provides a C interface, providing a relatively small API. Exposed functionality includes: parsing source code into an AST, loading ASTs, traversing the AST, associating source locations with elements within the AST.

## Status history

This table presents only significant steps and releases in Clang history.

Date  | Highlights

|

11 July 2007 | Clang front-end released under open-source licence
25 February 2009 | Clang/LLVM can compile a working FreeBSD kernel.[31][32]
16 March 2009 | Clang/LLVM can compile a working DragonFly BSD kernel.[33][34]
23 October 2009 | Clang 1.0 released, with LLVM 2.6 for the first time.
December 2009 | Code 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,[19] and can compile itself.[35]
2 February 2010 | Clang self-hosting.[36]
20 May 2010 | Clang latest version built the Boost C++ libraries successfully, and passed nearly all tests.[37]
10 June 2010 | Clang/LLVM becomes integral part of FreeBSD, but default compiler is still GCC.[38]
25 October 2010 | Clang/LLVM can compile a working modified Linux kernel.[39]
January 2011 | Preliminary work completed to support the draft C++0x standard, with a few of the draft's new features supported in Clang development version.[40][12]
10 February 2011 | Clang can compile a working HotSpot Java virtual machine.[25]
19 January 2012 | Clang becomes an optional component in NetBSD cross-platform build system, but GCC is still default.[41]
29 February 2012 | Clang 3.0 can rebuild 91.2% of the Debian archive.[42]
29 February 2012 | Clang becomes default compiler in MINIX 3[43]
12 May 2012 | Clang/LLVM announced to replace GCC in FreeBSD.[44]
5 November 2012 | Clang becomes default compiler in FreeBSD 10.x on amd64/i386.[45]
18 February 2013 | Clang/LLVM can compile a working modified Android Linux Kernel for Nexus 7.[46][47]
19 April 2013 | Clang is C++11 feature complete.[48]
6 November 2013 | Clang is C++14 feature complete.[49]
11 September 2014 | Clang 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.[50]
27 Feb 2015  | Clang 3.6.0 released. The default C version becomes `-std=gnu11`.
October 2016  | Clang becomes default compiler for Android[51] (and later only compiler supported by Android NDK[52]).
13 March 2017  | Clang 4.0.0 released
26 July 2017 | Clang becomes default compiler in OpenBSD 6.2 on amd64/i386.[53]
7 September 2017  | Clang 5.0.0 released
19 January 2018 | Clang becomes default compiler in OpenBSD 6.3 on arm.[54]
5 March 2018  | Clang is now used to build Google Chrome for Windows.[55]
8 March 2018  | Clang 6.0.0 released. The default C++ version becomes `-std=gnu++14`.
5 September 2018  | Clang is now used to build Firefox for Windows.[56]
19 September 2018  | Clang 7.0.0 released
20 March 2019  | Clang 8.0.0 released
1 July 2019 | Clang becomes default compiler in OpenBSD 6.6 on mips64.[57]
19 September 2019  | Clang 9.0.0 released with official RISC-V target support.[58]
29 February 2020  | Clang becomes the only C compiler in the FreeBSD base system, with the removal of GCC.[59]
24 March 2020  | Clang 10.0.0 released
2 April 2020 | Clang becomes default compiler in OpenBSD 6.7 on powerpc.[60]
12 October 2020  | Clang 11.0.0 released. The default C version becomes `-std=gnu17`.
21 December 2020 | Clang becomes default compiler in OpenBSD 6.9 on mips64el.[61]
14 April 2021  | Clang 12.0.0 released
4 October 2021  | Clang 13.0.0 released
25 March 2022  | Clang 14.0.0 released
6 September 2022  | Clang 15.0.0 released
17 March 2023  | Clang 16.0.0 released. The default C++ version becomes `-std=gnu++17`.
9 September 2023  | Clang 17.0.1 released
8 March 2024  | Clang 18.1.1 released
17 September 2024  | Clang 19.1.0 released
4 March 2025  | Clang 20.1.0 released
26 August 2025  | Clang 21.1.0 released

## See also

* AMD Optimizing C/C++ Compiler
* LLDB (debugger)
* Portable C Compiler

## References

1. ↑ "LLVM 2.1 Release Notes". LLVM Developer Group. 27 September 2007. https://www.llvm.org/releases/2.1/docs/ReleaseNotes.html.
2. ↑ "Releases". llvm – llvm-project repo. LLVM Developer Group. 27 August 2021. https://github.com/llvm/llvm-project/releases.
3. ↑ 3.0 3.1 3.2 LICENSE.TXT, LLVM Developer Group, https://releases.llvm.org/9.0.0/LICENSE.TXT, retrieved 2019-09-24
4. ↑ 4.0 4.1 4.2 LLVM Developer Policy, LLVM Developer Group, § Copyright, License, and Patents, https://llvm.org/docs/DeveloperPolicy.html#copyright-license-and-patents, retrieved September 12, 2021
5. ↑ Christopher, Eric (3 July 2008). "simply wonder pronunciation of Clang". LLVMdev (Mailing list). Retrieved 2015-09-22.
6. ↑ "OpenMP Support". May 22, 2015. http://blog.llvm.org/2015/05/openmp-support_22.html.
7. ↑ "C++ Heterogeneous-Compute Interface for Portability". https://github.com/ROCm-Developer-Tools/HIP.
8. ↑ "Clang Language Extensions". https://clang.llvm.org/docs/LanguageExtensions.html. "In addition to the language extensions listed here, Clang aims to support a broad range of GCC extensions."
9. ↑ 9.0 9.1 Clang - Features and Goals: GCC Compatibility, 15 April 2013, https://clang.llvm.org/features.html#gcccompat, retrieved April 30, 2018
10. ↑ "Clang Static Analyzer". LLVM. https://clang-analyzer.llvm.org/.
11. ↑ Getting Involved with the Clang Project, LLVM Developer Group, https://clang.llvm.org/get_involved.html, retrieved 2012-09-18, "Clang is a subproject of the LLVM Project, but has its own mailing lists because the communities have people with different interests."
12. ↑ 12.0 12.1 "C++ and C++'0x Support in Clang". LLVM. https://clang.llvm.org/cxx_status.html.
13. ↑ "Clang 17.0.1 Release Notes". LLVM. https://releases.llvm.org/17.0.1/tools/clang/docs/ReleaseNotes.html.
14. ↑ Treat, Adam (19 February 2005). "mkspecs and patches for LLVM compile of Qt4". Qt4-preview-feedback (Mailing list). Archived from the original on 4 October 2011.
15. ↑ Lattner, Chris (25 May 2007). "LLVM for OpenGL and other stuff" (Slides). LLVM Developers' Meeting. https://llvm.org/devmtg/2007-05/10-Lattner-OpenGL.pdf. Retrieved April 30, 2018.
16. ↑ Zadeck, Kenneth (19 November 2005). "Re: LLVM/GCC Integration Proposal". GCC development (Mailing list). Archived from the original on March 10, 2016. Retrieved July 25, 2016.
17. ↑ 17.0 17.1 Naroff, Steve (25 May 2007). "New LLVM C Front-end" (Slides). LLVM Developers' Meeting. https://llvm.org/devmtg/2007-05/09-Naroff-CFE.pdf. Retrieved April 30, 2018.
18. ↑ Lattner, Chris (11 July 2007). "New LLVM C front-end: "clang"". cfe-dev (Mailing list). Archived from the original on March 26, 2020. Retrieved March 26, 2020.
19. ↑ 19.0 19.1 Clang team, clang: a C language family frontend for LLVM
20. ↑ "Clang: Utility and Applications: Library Based Architecture". https://clang.llvm.org/features.html#libraryarch.
21. ↑ "FLANG: NVIDIA Brings Fortran To LLVM". https://phoronix.com/scan.php?page=news_item&px=LLVM-NVIDIA-Fortran-Flang.
22. ↑ "Welcome to Flang's documentation — the Flang Compiler". https://flang.llvm.org/docs/.
23. ↑ Clang can often be used as a drop-in replacement for GCC, May 2020, https://clang.llvm.org/get_started.html#driver, retrieved May 9, 2020
24. ↑ Clang - Features and Goals: Fast compiles and Low Memory Use, October 2007, https://clang.llvm.org/features.html, retrieved April 30, 2018
25. ↑ 25.0 25.1 25.2 Simonis, Volker (10 February 2011). "Compiling the HotSpot VM with Clang". https://weblogs.java.net/blog/simonis/archive/2011/02/10/compiling-hotspot-vm-clang. "While the overall GCC compatibility is excellent and the compile times are impressive, the performance of the generated code is still lacking behind a recent GCC version. "
26. ↑ "Benchmarking LLVM & Clang Against GCC 4.5". Phoronix. 21 April 2010. https://www.phoronix.com/scan.php?page=article&item=gcc_llvm_clang&num=6. "Binaries from LLVM-GCC and Clang both struggled to compete with GCC 4.5.0 in the timed HMMer benchmark of a Pfam database search. LLVM-GCC and Clang were about 23% slower(...)Though LLVM / Clang isn't the performance champion at this point, both components continue to be under very active development and there will hopefully be more news to report in the coming months"
27. ↑ 27.0 27.1 "GCC 4.9 VS. LLVM Clang 3.5 Linux Compiler Benchmarks". OpenBenchmarking.org. 14 April 2014. https://openbenchmarking.org/result/1404144-KH-CLANG359076.
28. ↑ 28.0 28.1 Michael Larabel (Dec 23, 2019). "LLVM Clang Achieves ~96% The Performance Of GCC On Intel Ice Lake". https://www.phoronix.com/scan.php?page=news_item&px=GCC-LLVM-Clang-Icelake-Tests.
29. ↑ "Clang vs GCC - which produces better binaries?". https://stackoverflow.com/questions/3187414/clang-vs-gcc-which-produces-better-binaries#15043814.
30. ↑ Michael Larabel (May 11, 2023). "LLVM Clang 16 vs. GCC 13 Compiler Performance On Intel Raptor Lake". https://www.phoronix.com/review/gcc13-clang16-raptorlake/5.
31. ↑ Divacky, Roman (February 25, 2009). "[Announce] clang/llvm can compile booting FreeBSD kernel on i386/amd64". https://lists.freebsd.org/pipermail/freebsd-current/2009-February/003743.html.
32. ↑ Building FreeBSD with Clang, Wiki.freebsd.org, 2012-08-24, https://wiki.freebsd.org/BuildingFreeBSDWithClang, retrieved 2012-09-18
33. ↑ Hornung, Alex. "llvm/clang once more". https://leaf.dragonflybsd.org/mailarchive/kernel/2009-03/msg00067.html.
34. ↑ Clang, DragonFly BSD, https://www.dragonflybsd.org/docs/developer/clang/, retrieved 2012-09-18
35. ↑ "Clang can compile LLVM and Clang". LLVM Project Blog. December 24, 2009. http://blog.llvm.org/2009/12/clang-builds-llvm.html.
36. ↑ "Clang Successfully Self-Hosts". LLVM Project Blog. February 4, 2010. http://blog.llvm.org/2010/02/clang-successfully-self-hosts.html.
37. ↑ Gregor, Doug (May 20, 2010). "Clang++ Builds Boost!". LLVM Project Blog. http://blog.llvm.org/2010/05/clang-builds-boost.html.
38. ↑ Davis, Brad. "FreeBSD Status Reports April–June, 2010". https://www.freebsd.org/news/status/report-2010-04-2010-06.html#Clang-Replacing-GCC-in-the-Base-System.
39. ↑ Clang builds a working Linux Kernel (Boots to RL5 with SMP, networking and X, self hosts), Lists.cs.uiuc.edu, http://lists.cs.uiuc.edu/pipermail/cfe-dev/2010-October/011711.html, retrieved 2012-09-18
40. ↑ Gregor, Douglas (26 January 2011). "New C++0x feature support in Clang" (Mailing list). Archived from the original on 30 January 2011. Retrieved 29 January 2011.
41. ↑ Sonnenberger, Jörg (2012-01-19). "Status of NetBSD and LLVM". https://www.sonnenberger.org/2012/01/19/status-netbsd-and-llvm/.
42. ↑ Ledru, Sylvestre. "Rebuild of the Debian archive with clang". https://sylvestre.ledru.info/blog/2012/02/29/rebuild_of_the_debian_archive_with_clang.
43. ↑ "Official Minix 3 website: News". http://www.minix3.org/news/.
44. ↑ Gerzo, Daniel (12 May 2012). "FreeBSD Quarterly Status Report January–March, 2012" (Mailing list). Archived from the original on February 18, 2018. Retrieved 14 May 2012.
45. ↑ Davis, Brooks (5 November 2012). "Heads Up: Clang now the default on x86" (Mailing list). Archived from the original on April 30, 2018. Retrieved 7 November 2012.
46. ↑ Webster, Behan (18 February 2013). "LLVMLinux: Compiling Android with LLVM". https://events.linuxfoundation.org/images/stories/slides/abs2013_webster.pdf.
47. ↑ Tinti, Vinicius (17 March 2013). "LLVMLinux: Nexus 7". https://llvm.linuxfoundation.org/index.php/Nexus_7.
48. ↑ Du Toit, Stefanus. "Clang is C++11 feature complete as of *just now*!". https://twitter.com/sdt_intel/status/325289093170864129.
49. ↑ "[llvm-project Revision 194194"]. https://llvm.org/viewvc/llvm-project?view=revision&revision=194194.
50. ↑ Ledru, Sylvestre. "Rebuild of Debian using Clang 3.5.0". https://sylvestre.ledru.info/blog/2014/09/11/rebuild-of-debian-using-clang-3-5.
51. ↑ "NDK Revision History | Android Developers" (in en). https://developer.android.com/ndk/downloads/revision_history.html.
52. ↑ "NDK Revision History | Android NDK | Android Developers" (in en). https://developer.android.com/ndk/downloads/revision_history.
53. ↑ Nagy, Robert (26 July 2017). "switch the default compiler on amd64 and i386 to clang" (Mailing list). Archived from the original on October 25, 2018. Retrieved 30 September 2017.
54. ↑ Kettenis, Mark (19 January 2018). "Switch the default compiler on armv7 to clang" (Mailing list). Archived from the original on April 8, 2022. Retrieved 27 August 2020.
55. ↑ "Clang is now used to build Chrome for Windows". March 5, 2018. http://blog.llvm.org/2018/03/clang-is-now-used-to-build-chrome-for.html.
56. ↑ "Firefox Beta 63.0beta, See All New Features, Updates and Fixes" (in en). https://www.mozilla.org/en-US/firefox/63.0beta/releasenotes/.
57. ↑ Hankala, Visa (1 July 2019). "Switch the default compiler on octeon to clang" (Mailing list). Archived from the original on April 8, 2022. Retrieved 27 August 2020.
58. ↑ "LLVM 9 Releases With Official RISC-V Target Support, Asm Goto, Clang 9, And More". 26 September 2019. https://riscv.org/2019/09/llvm-9-releases-with-official-risc-v-target-support-asm-goto-clang-9-and-more-vincy-davis-packt-pub/.
59. ↑ "FreeBSD svn commit r358454". February 29, 2020. https://lists.freebsd.org/pipermail/svn-src-all/2020-February/194446.html.
60. ↑ Kettenis, Mark (2 April 2020). "Switch the default compiler on powerpc to clang" (Mailing list). Archived from the original on April 8, 2022. Retrieved 27 August 2020.
61. ↑ Hankala, Visa (21 December 2020). "Make clang the default compiler on loongson" (Mailing list). Archived from the original on January 13, 2021. Retrieved 1 January 2021.

## External links

* No URL found. Please specify a URL here or add one to Wikidata.

0.00

(0 votes)

Original source: https://en.wikipedia.org/wiki/Clang. Read more

|

Retrieved from "https://handwiki.org/wiki/index.php?title=Software:Clang&oldid=4219258"