Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suppress repeated analysis warnings about the same translation unit #11

Closed
lambdageek opened this issue Oct 31, 2017 · 1 comment
Closed

Comments

@lambdageek
Copy link
Owner

lambdageek commented Oct 31, 2017

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

@lambdageek lambdageek changed the title Suppress repeated analysis warnings about the same declaration Suppress repeated analysis warnings about the same translation unit Nov 8, 2017
@lambdageek lambdageek added this to the 0.1 MVP milestone Nov 8, 2017
@lambdageek
Copy link
Owner Author

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).

lambdageek added a commit that referenced this issue Nov 8, 2017
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
lambdageek added a commit that referenced this issue Nov 8, 2017
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant