Permissive licenses, community, and copyleft
Permissive licenses, community, and copyleft
Posted Nov 16, 2015 21:51 UTC (Mon) by jwakely (subscriber, #60262)In reply to: Permissive licenses, community, and copyleft by Cyberax
Parent article: Permissive licenses, community, and copyleft
> There's already a production-grade SPIR-V backend for LLVM, while a gcc backend is still being talked about.
Oh, so when LLVM has something announced, but at least a year from existing, that's a plus point for LLVM, but when LLVM has something existing and GCC is only talking about it, that's also a plus point for LLVM. You should try to make it a bit less obvious when twisting facts to suit your agenda.
Newsflash: GCC already has a high quality Fortran front-end, with vectorization.
> I'm pretty sure that the development focus has shifted from GCC, permanently.
What does "the development focus" mean?! If you mean loudmouths on the internet who contribute nothing to either project are spending their time hyping LLVM, I must agree. As far as actual development goes, both projects seem active and healthy to me.
Posted Nov 17, 2015 5:25 UTC (Tue)
by Cyberax (✭ supporter ✭, #52523)
[Link]
> What does "the development focus" mean?! If you mean loudmouths on the internet who contribute nothing to either project are spending their time hyping LLVM, I must agree.
Do you know anything exciting happening lately with gcc? It still has some momentum and a lot of developers are more familiar with it (so it gets new C++ features faster), but it's clearly fading.
Permissive licenses, community, and copyleft
Yup. It means that companies are actively investing in LLVM to the point where it's going to dominate everything else. And it will happen within a year or so.
It means that when you're starting a new project, you first go to LLVM and not gcc. E.g.: Rust, BEAMJIT ( https://lup.lub.lu.se/student-papers/search/publication/5... ), Pyston, beignet, ...