Update LLVM's license to Apache 2.0 #25969
Conversation
While reviewing some of our third-party licenses, I happened to notice that the copy of LLVM we redistribute is actually Apache 2.0 licensed, meaning our file was out of date. Jade and Michael checked my work: Jade: Looks like the last release with UIUC license was LLVM 8. https://github.com/llvm/llvm-project/blob/release/8.x/llvm/LICENSE.TXT EDIT: some later releases have legacy licenses with UIUC Michael: License was changed in ``` commit 469bdefd448b76c5adcdd67256e9a44fabf7e027 Author: Chandler Carruth <chandlerc@gmail.com> Date: Sat Jan 19 06:14:24 2019 +0000 ``` Docs https://llvm.org/docs/DeveloperPolicy.html#legacy indicate some LLVM stuff still uses the old license. I have no idea what. LLVM proper and Clang don't seem to. --- Signed-off-by: Brad Chamberlain <bradcray@users.noreply.github.com>
|
@jabraham17 / @mppf : Tagging you as an FYI and thanks for your help. I don't think this actually needs a review, though. |
|
Here is my recommended PR message wording. While reviewing some of our third-party licenses, I happened to notice that the copy of LLVM we redistribute is actually Apache 2.0 licensed, meaning our file was out of date. The last release with UIUC license was LLVM 8 although some later releases have legacy licenses with UIUC. The license was changed to Apache License v2.0 with LLVM Exceptions in llvm-project commit 469bdefd448b76c5adcdd67256e9a44fabf7e027 in Jan 2019. Docs https://llvm.org/docs/DeveloperPolicy.html#legacy indicate some of LLVM still uses the old license but as far as we know, nothing that Chapel uses falls into that category. |
While reviewing some of our third-party licenses, I happened to notice that the copy of LLVM we redistribute is actually Apache 2.0 licensed, meaning our file was out of date.
The last release with UIUC license was LLVM 8 although some later releases have legacy licenses with UIUC.
The license was changed to Apache License v2.0 with LLVM Exceptions in llvm-project commit 469bdefd448b76c5adcdd67256e9a44fabf7e027 in Jan 2019.
Docs https://llvm.org/docs/DeveloperPolicy.html#legacy indicate some of LLVM still uses the old license but as far as we know, nothing that Chapel uses falls into that category.