-
Notifications
You must be signed in to change notification settings - Fork 463
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
Propagated coverage flags cause gcov
link errors
#1354
Comments
CC @mrkajetanp.
I think that'd be a reasonable fix. |
Huh interesting, I didn't realise gcc and clang actually used different formats for the profiling. Yeah in this case there's no point passing it to gcc I agree, would you like me to write up a PR? |
@mrkajetanp If you're inclined, please go ahead! Otherwise I'll try to get to it later this weekend. |
Clang and GNU use different PGO libraries, so PGO flags inherited from rustc should not automatically be passed to GNU compilers. Fixes rust-lang#1354
Clang and GNU use different PGO libraries, so PGO flags inherited from rustc should not automatically be passed to GNU compilers. Fixes rust-lang#1354
Clang and GNU use different PGO libraries, so PGO flags inherited from rustc should not automatically be passed to GNU compilers. Fixes #1354
When compiling code like the example and
RUSTFLAGS=-Cprofile-generate=$PWD
, it fails to link with errors like this:(and many other
__gcov_*
symbols)That's with a default
CC
that is GCC; it's okay with Clang because that uses the same profiling library as Rust.Maybe
-Cprofile-generate
(and-Cprofile-use
) should not be translated forToolFamily::Gnu
at all? It seems unlikely that someone would use this and try to juggle both LLVMprofraw
and GCCgcov
files, even if the link error is fixed.The text was updated successfully, but these errors were encountered: