3 ms·
Title adapted from the prior submission [1] ("RMS regrets not accepting LLVM into GCC during 2005") but reworded so that it's clear RMS didn't know its contents
by lifthrasiir 6y ago
Title adapted from the prior submission [1] ("RMS regrets not accepting LLVM into GCC during 2005") but reworded so that it's clear RMS didn't know its contents beforehand.
(EDIT: My original title was "RMS regrets missing an email for the 2005 LLVM/GCC Integration Proposal (2015)", which was reworded by the moderator to match the earlier submission. I don't exactly like the rewording, but am fine with that.)
The actual Integration Proposal [2] proposed an adapter from GIMPLE to LLVM BC so that GCC can make use of LLVM optimization passes without much hassle. Lattner (on behalf of Apple) was willing to assign the copyright of the entire LLVM once it became a preferred backend of GCC. Remember this was before GPLv3 (2007). It is not hard to imagine an alternative universe where this actually happened and GCC remains the dominant free/libre compiler.
[1] https://news.ycombinator.com/item?id=9028738 https://news.ycombinator.com/item?id=9028738
[2] https://gcc.gnu.org/legacy-ml/gcc/2005-11/msg00888.html https://gcc.gnu.org/legacy-ml/gcc/2005-11/msg00888.html
- hyperman1 6y agoI understood Apple choose and funded LLVM explicitly because they wanted to decrease their dependency on GPL-licensed software. If LLVM moved under the FSF-flag, that funding would presumably dry up, or Apple would fork LLVM. I don't see the alternative universe happening. Besides, GCC fell a bit asleep once until EGCS kicked them awake, and again until LLVM appeared. A bit of competition seems healthy to keep everyone awake, and having both projects managed by the same organisation is a risk here. To be clear, GCC is and stays a great product and LLVM probably needs GCC as much as the other way around.