[cfe-dev] Analyzer messages output
Jordan Rose
jordan_rose at apple.com
Thu Aug 22 17:03:43 PDT 2013
Hi, fiveight. Currently, we don't have any such plan. It's not infeasible, but it means the set of diagnostic messages the analyzer can emit is fixed at compile time. There's no inherent downside to that (other than having to recompile much more of Clang when the set of analyzer diagnostics and path notes changes), but it does make it harder for people to write analyzer plugins that introduce new checkers and new diagnostics. I can't see a practical benefit to changing over right now.
(The analyzer plugin mechanism isn't so actively maintained, but I know there are at least a couple people/companies using it for their own internal purposes.)
Jordan
On Aug 21, 2013, at 18:30 , fiveight <fiveight at tom.com> wrote:
> Hi All:
>
> I find clang put all diagnostic messages into .td files, but did not put all static analyzer messages into .td files, just part of them.
> Is there any plan to put these messages all into .td files?
>
> Thanks.
>
>
> fiveight
> fiveight at tom.com
> 2013-08-22
>
> _______________________________________________
> cfe-dev mailing list
> cfe-dev at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
More information about the cfe-dev
mailing list