http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19165
--- Comment #18 from Manuel López-Ibáñez <manu at gcc dot gnu.org> 2013-03-27 00:59:43 UTC --- (In reply to comment #17) > (In reply to comment #16) > > > > If you have some developer power to spare, it may be worthwhile to try to > > tackle this yourself. Otherwise I am afraid this will never be implemented > > in > > GCC. The patch in comment #10 is very rough and outdated, but the idea is > > simple. Copy diagnostic.c to diagnostic-xml.c and start modifying the output > > functions to emit XML. > Probably, I can spare some time, but I don't have time to spare and be > bothered > with all the copyright assignments and other bureaucracy related things. Unfortunately, and from my own experience, I completely understand your position. Worse, the amount of bureaucracy required seems to be random. I would suggest to give it a token try, by sending an email to both g...@gnu.gcc.org and assignme...@gcc.org, perhaps trying to opt for a copyright disclaimer instead. See http://gcc.gnu.org/contribute.html#legal If you find the process too troublesome, well, nobody can said you didn't try. But it would be good to announce your decision to give up in both mailing lists, as it is difficult to estimate how many people don't contribute to gcc just because of the bureaucracy (Although I believe the number to be larger than the number of current contributors, sadly).
