http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19165
--- Comment #16 from Manuel López-Ibáñez <manu at gcc dot gnu.org> 2013-01-30 18:18:35 UTC --- (In reply to comment #15) > I'm speaking as one of Code::Blocks' developers: > If you implement this we'll for sure use it, because we have many complaints > similar to the one Eclipse's developers have. 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. > Don't pack the line/column info with the file name, if possible. This will be trivial to do. > Also, if it is possible group the notes/instances info with the error/warning > messages. This way it will allows us to show the information in a better way. This will be more complicated, because the diagnostics machinery does not have a concept of multiple messages belonging to the same diagnostic. But I think this is eventually the way to go (and I think Gabriel, the diagnostics maintainer, thinks the same) by the way of defining an internal representation for diagnostics output. (http://gcc.gnu.org/ml/gcc/2012-04/msg00567.html) Dumping this internal representation in XML format would be easy then. But designing and implementing this IR does not seem trivial, so you may want to start with the simple stuff.
