[PATCH] D22494: [analyzer] Explain why analyzer report is not generated (fix for PR12421).

Anton Yartsev via cfe-commits cfe-commits at lists.llvm.org
Tue Jul 26 07:54:07 PDT 2016


ayartsev added inline comments.

================
Comment at: test/Analysis/PR12421.c:11
@@ +10,2 @@
+
+// CHECK: warning: Path diagnostic report is not generated. HTMLDiagnostics does not support diagnostics that cross file boundaries.
----------------
zaks.anna wrote:
> We should use the name of the diagnostic consumer here - that will only be legible for the developers working on the attic analyzer core. 
Done. As for me the name of the diagnostic consumer also makes the warning more clear and helpful for an ordinary user. From the consumer name he can see what report format is talked about and maybe change the scan-build (which setups the '-analyzer-output' frontend option internally) options. Do you still want to remove the consumer name from the warning?


https://reviews.llvm.org/D22494





More information about the cfe-commits mailing list