> > Forgive me, but I'm a little stumped here. When did GCC move to a > > "non-open" license? It didn't > About when it decided anti-tivoization was within its mandate, so A lot of consider the GPLv2 license has the same requirement > That said, reducing code duplication is a good thing. I'm just not > convinced "how well gcc 4.6 optimizes this" is the only relevant test > criteria here. It is for the other 99.999999999% of users. > LLVM/CLANG is bsd licensed (alas, with advertising clause, but code from > it might actually be incorporatable into the linux kernel, unlke gcc, > which is under a license extensively incompatible with the linux kernel). Advertising clause BSD is not GPL compatible. > Ok, so "designed with gcc 4.6's optimizer in mind, regression tested > back to 3.4 for at least minimal functionality, and not intentionally > breaking other compilers". If you want it to work with weird cornercase compilers its for your benefit so it's your problem and you do the work. Thats how free software works. At the point lots of people starting using your compiler it might matter more and if everyone starts using your compiler then it'll end up being the primary optimisation target. Alan -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
