You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In --project mode if the same translation unit appears multiple times in the compilation database, only run the analysis once and just record that the other occurrences in compile_commands were skipped.
This is a good way to keep the JSON output smaller for #8
The text was updated successfully, but these errors were encountered:
lambdageek
changed the title
Suppress repeated analysis warnings about the same declaration
Suppress repeated analysis warnings about the same translation unit
Nov 8, 2017
For MVP we should only avoid re-running the analysis if the compile_commands.json compilation database has multiple runs over the same file. (for example - mono builds its metadata/ directory 4 times if you build both Sgen and Boehm each dynamically and statically).
If there are multiple compiler invocations captured in the JSON compilation
database, just pick one arbitrarily to analyze and emit a debug note about the
others (on stderr, not in the report).
Closes#11
If there are multiple compiler invocations captured in the JSON compilation
database, just pick one arbitrarily to analyze and emit a debug note about the
others (on stderr, not in the report).
Closes#11
In
--project
mode if the same translation unit appears multiple times in the compilation database, only run the analysis once and just record that the other occurrences in compile_commands were skipped.This is a good way to keep the JSON output smaller for #8
The text was updated successfully, but these errors were encountered: