Is Apple Now Blocking Contributions To GCC?

Apple isn't blocking contributions, they just don't care about them anymore since they're going with LLVM/Clang. And since they don't care they don't have the legal framework in place anymore to do copyright assignments.<p>The FSF could have these changes if they wanted if they didn't require copyright assignment.<p>Personally I don't contribute to FSF projects because copyright assignments are a PITA. I can see how a company that doesn't <i>need</i> to contribute to GCC anymore just doesn't care enough to initiate the requisite legal work.

The headline is misleading. Chris Lattner's post actually just points out that FSF's own copyright-assignment policy may be a blocker:<p><i>"...In practice, since the FSF cares about copyright assignment, this probably means that..."</i><p><a href="http://www.gnu.org/licenses/why-assign.html" rel="nofollow">http://www.gnu.org/licenses/why-assign.html</a>

Although the underlying story is interesting, I'm not going to vote up this particular article due to the horribly misleading title.

Phoronix. The tabloid of free software geek news website. Their best known speciality: sensationalist articles based on ridiculous benchmarks.

Seems to me that the original article writer is flamebaiting and being deliberately inflammatory with his assumptions. I'd say the main issue here is that Apple does not agree with the GPL license family (which we all know since long; they've voiced this before), and that they don't really care for GCC anymore now that they have set aim for Clang-LLVM.