|
|
|
|
|
by lazyjones
4538 days ago
|
|
> GCC is written poorly on purpose in order to make it difficult to work with gcc That's a strange conspiracy theory that has been posted here several times and debunked as well. It seems particularly odd to me because when I worked at a university 15 years ago, everyone in the compiler research world would occasionally hack on gcc to add features, retarget it, add optimizations etc. ... It didn't seem prohibitively difficult. |
|
For example RMS vetoed the first attempts to add support for Java bytecode to GCC because he thought it would allow people to interact with GCC from other non-free software: http://gcc.gnu.org/ml/gcc/2001-02/msg00895.html
That same reasoning is why there is no GCC equivalent to LLVM IR or libclang or libtooling.
https://lists.gnu.org/archive/html/emacs-devel/2012-12/msg00...
Part of the reason why clang/llvm weakens our commnity, compared with GCC, is that the clang front ends can feed their data to nonfree tools.
There are some links in this wiki page that cover some of the arguments made against adding support for plugins to GCC. http://gcc.gnu.org/wiki/GCC_Plugins under 'Potential disadvantages of supporting a plugin architecture in GCC'
Here is a post from a GCC maintainer explaining that RMS was personally blocking the inclusion of this much desired basic functionality for political reasons: http://gcc.gnu.org/ml/gcc/2007-11/msg00193.html
> Is there any progress in the gcc-plugin project ?
Non-technical holdups. RMS is worried that this will make it too easy to integrate proprietary code directly with GCC.