3 ms·
Hm... I don't quite buy that as the whole story. The gcc stuff may all be true (I certainly don't have any knowledge otherwise), but I don't see where it gener
by ajross 12y ago
Hm... I don't quite buy that as the whole story. The gcc stuff may all be true (I certainly don't have any knowledge otherwise), but I don't see where it generalizes to clang/LLVM.
Apple certainly isn't wishing they could "get more changes into" LLVM, they're deliberately witholding the extensive changes they have. The iOS 64 bit toolchain is an almost completely closed-source thing, despite being derived from a free software base. If Apple "gave not a crap" about releasing source, they had an obvious path to do so. That they haven't (and that they've invited PR messes like this argument) implies to me that they don't want to release it.
- DannyBee 12y ago" The iOS 64 bit toolchain is an almost completely closed-source thing, despite being derived from a free software base." It would have been this way with GCC too. They had already written their own linker, etc. Apple didn't give a crap about releasing GCC patches, because it was not for an architecture they controlled. Much like embedded gcc developers often do, for architectures they control, they are probably just delaying the release until it no longer provides what they perceive to be a competitive advantage. They would have done this with GCC too (and did in the past!)