-
Notifications
You must be signed in to change notification settings - Fork 19
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
Performance regression with rustc 1.30.0-nightly (2ab3eba30 2018-09-14) #35
Comments
Thanks for the report. Which OS are you using, and are the cargo-kcov version between 09-06 and 10-01 the same? |
I'm using FreeBSD 11.2 amd64. I haven't checked any nightly compilers between 09-06 and 10-01. |
Thanks.
I mean the version of |
Oh, sorry. I'm using cargo-kcov 0.5.0. |
Same results with cargo-kcov 0.5.2. |
I bisected the compiler version. The slowdown was introduced in rustc 1.30.0-nightly (2ab3eba30 2018-09-14). It was not present in rustc 1.30.0-nightly (90d36fb59 2018-09-13). |
Thanks. The range rust-lang/rust@90d36fb...2ab3eba contains quite many PRs, but I think it's caused by cargo-kcov not updated to properly handle rust-lang/rust#53829. |
Wow! Cool that you found it so quickly. I'm going to leave it to you then, unless you need any more help from me. |
Hm, it looks like upstream may have fixed things already. The problem is gone with the latest compiler. In fact, it's faster than ever before. Version rustc 1.31.0-nightly (de9666f12 2018-10-31) takes 6.08s. |
Running
cargo kcov
is much slower with recent compilers. For example, asomers/futures-locks takes:nightly-2018-09-06-x86_64: 18.38s
nightly-2018-10-01-x86_64: 61.46s
nightly-2018-10-15-x86_64: 61.14s
1.30.0 (da5f414c2 2018-10-24): 60.08s
I don't know if this is a problem with rustc or cargo-kcov, but I haven't noticed any problems except when using kcov.
The text was updated successfully, but these errors were encountered: