Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Only the old LLVM license is used #87

Open
hikari-no-yume opened this issue Feb 23, 2021 · 1 comment · May be fixed by #173
Open

Only the old LLVM license is used #87

hikari-no-yume opened this issue Feb 23, 2021 · 1 comment · May be fixed by #173

Comments

@hikari-no-yume
Copy link
Collaborator

LLVM moved to a new license a while ago. This backend is still using the old one.

For new contributions, would it make sense to dual-license them for easier reuse in other LLVM code?

For the existing code, I assume it can't just be marked as using the new license, since it's based on upstream LLVM code that got deleted and thus wouldn't have been relicensed, right?

@hikari-no-yume hikari-no-yume changed the title License Only the old LLVM license is used Feb 24, 2021
@hikari-no-yume
Copy link
Collaborator Author

hikari-no-yume commented Mar 7, 2021

For the existing code, I assume it can't just be marked as using the new license, since it's based on upstream LLVM code that got deleted and thus wouldn't have been relicensed, right?

Actually, I hadn't thought about how the old LLVM licence allows sublicensing. It probably can “just” be changed to the new licence. That's what upstream LLVM did.

(This also means that, for me at least, the licensing is not an urgent matter. I can contribute code under the old licence and just relicense later if necessary.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant