https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67250
--- Comment #14 from Manuel López-Ibáñez <manu at gcc dot gnu.org> --- (In reply to Jeff Hammond from comment #13) > This is all fair. I try very hard to fix my own bugs and submit patches, > but in this case I am wholly unqualified. I don't know the first thing > about implementing a production compiler, or any compiler for that matter. To work on GCC, you mostly need to know C/C++, how to use GDB and be able to setup the bootstrap and regression test environment. Most tasks are not hard or require any special knowledge, just tedious (run the testsuite, follow-up on patches, trace code through the debugger and figure out why it is not working as it should). In fact, GCC is not lacking patches, there are many unapplied patches in bugzilla and the mailing lists. It lacks people motivated enough to do all the red-tape work necessary to get a patch applied to the repository.
