-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
coverage: Move most per-function coverage info into mir::Body
#116046
Merged
Merged
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
c479bc7
coverage: Attach an optional `FunctionCoverageInfo` to `mir::Body`
Zalathar a18c5f3
coverage: Store the number of counters/expressions in function covera…
Zalathar 79f935b
coverage: Rename `Operand` to `CovTerm`
Zalathar 8efdd4c
coverage: Collect a function's coverage mappings into a single list
Zalathar 4099ab1
coverage: Make expression simplification non-destructive
Zalathar 6da319f
coverage: Store all of a function's mappings in function coverage info
Zalathar 7d38f4a
Remove unused `TyCtxt` from `remove_dead_blocks`
Zalathar 13b2d60
coverage: Store expression data in function coverage info
Zalathar 753caf2
coverage: Update docs for `StatementKind::Coverage`
Zalathar 33da097
coverage: Explicitly note that counter/expression IDs are function-local
Zalathar File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
344 changes: 153 additions & 191 deletions
344
compiler/rustc_codegen_llvm/src/coverageinfo/map_data.rs
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we use
function_coverage_info.num_counters
and remove the query altogether?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I had originally wanted to do that, but eventually decided against it, for two reasons:
.profraw
files. So in cases where high-numbered counters are removed by MIR opts, this reduces the overall size of the profile data. Removing the query now would make profile data larger than before, in cases where it's currently making a difference.