You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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.)
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?
The text was updated successfully, but these errors were encountered: