http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55115
--- Comment #9 from Manuel López-Ibáñez <manu at gcc dot gnu.org> 2012-10-29 15:13:33 UTC --- (In reply to comment #8) > (In reply to comment #5) > > Or even better, use libClang <http://clang.llvm.org/docs/Tooling.html> to do > > what you want instead of parsing GCC errors, which are likely to change in > > unexpected ways. > > Did GCC team told me to go on clang side to fix my gcc issues ? :-D Just trying to help! :-D GCC is not really ready for this type of use. But you can try to develop a gcc plugin: http://gcc.gnu.org/wiki/plugins, and contribute to GCC any functionality missing for your plugin. But I honestly think the workarounds Jonathan and I have proposed should be more than enough to fix your problem.
