The results have been summed up of the initiative to transfer the LLVM project from the BSD-like UIUC/NCSA license to the Apache 2.0 license LLVM exceptions added for compatibility with GPLv2 and to solve licensing problems when including parts of the compiler and runtime libraries in executable files. Because the LLVM project does not require developers to sign an agreement to transfer ownership of the code, changing the license requires explicit consent from all participants. Relicensing began in 2018 and in 8 years it was possible to obtain consent to change the license from more than 1,300 developers and about 100 companies.
Code added after January 19, 2019 was accepted under a new license, so the main goal of the initiative was to obtain consent from the developers of past changes. Currently, 99.5% of the project’s code base is covered by the new license or is not subject to copyright (changes in less than 10 lines of code). Continuing to find developers to cover the remaining 0.5% is seen as pointless. Those who disagree with the license change can contact the project and their code will be marked accordingly in the SPDX metadata.
After the release of LLVM 24, which is scheduled for early 2027, the next branch of LLVM 25 will ship with updated LICENSE files and relevant license information in the code files. Third-party libraries integrated into LLVM will retain their own licenses.
The main reason for changing the license to Apache 2.0 is to protect users and contributors from patent lawsuits and to relieve companies wishing to participate in development from the hassle of transferring proprietary technology. The Apache 2.0 license requires the right to use patents associated with open source code, and includes clauses to minimize the risks of patent lawsuits (the license is revoked in the event of a patent lawsuit against the creator of the open source code).
The change in license also helped get rid of the inconsistency in licenses for runtime libraries and other components of the compiler, which prevented the exchange of code with runtime (compiler_rt was supplied under the bundle UIUC/NCSA and MIT, and the compiler is only for UIUC/NCSA). Among the advantages of Apache 2.0, one-sided compatibility with the GPLv3 license is mentioned, allowing you to use code under the Apache 2.0 license in projects under the license GPLv3.
The incompatibility with GPLv2 was overcome by adding a special exception that discards some sections of the Apache 2.0 license when using code in applications under the GPLv2 license in the event of a licensing conflict or litigation. The exception only applies to combination products that combine LLVM code with GPLv2-licensed code. The added exception also includes a clause that removes the requirement of the Apache 2.0 license to maintain copyright notices, attach license text, and note changes for compiler components and runtime libraries.
added to object and executable files.