-
-
Notifications
You must be signed in to change notification settings - Fork 57
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
Code compiled with different #[cfg] flags shows up as different instantiations #344
Comments
As taiki-e said in the other thread this is a problem of LLVM and not much can be done in cargo-llvm-cov about it. The coverage profiles should be merged but llvm-cov/llvm-profdata would need to do that. |
(I'm wondering if this may be another instance of #325.) |
It almost certainly is. I am also pleasantly surprised that I was wrong and that the issue can be solved with a demangler even with current LLVM implementation! That is great news and could improve teh quality of the coverage reporting. |
This probably has been fixed in v0.6.7 (#354). Could you recheck this with v0.6.7? |
Thanks for this, I have tried it and I see no missing lines with multiple instantiations anymore as long as the coverage overlaps. The only remaining issue is |
Thanks for confirming!
Yeah, it's different rustc bug: rust-lang/rust#98712 |
Initially reported by @Dushistov here:
Oh, that's why not generic functions some times have several instantiation according to html generated by cargo-llvm-cov:
The solution might end up being the same as #43
The text was updated successfully, but these errors were encountered: