https://gcc.gnu.org/bugzilla/show_bug.cgi?id=46476
--- Comment #14 from Manuel López-Ibáñez <manu at gcc dot gnu.org> --- (In reply to Jon Grant from comment #13) > May be simpler to just implement these static analysis checkers outside of a > compiler. Or as a plugin to GCC (so that it reuses GCC internals) that is stored in GCC source repository and build alongside. But the main barrier for this is not technical or acceptance, it is leadership and human resources. Someone has to take care of such a project, find developers and commit to maintain it. For various (bad) reasons, people tend to prefer to develop their personal in-house ad-hoc solution, rather than work with others with similar goals and with the GCC community. The end result is that existing solutions are poor, not widely used and often abandoned. On the other hand, there are many examples to follow on how to approach such a project. This includes all the enhancements to diagnostics done by non-core developers, libcc1, the D front-end, every new target added by non-core developers, etc.
