-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Fix dylib+rlib with LTO. #8754
Fix dylib+rlib with LTO. #8754
Conversation
r? @Eh2406 (rust_highfive has picked a reviewer for you, use r? to override) |
@bors: r+ |
📌 Commit 90e286d has been approved by |
☀️ Test successful - checks-actions |
Update cargo 3 commits in 75615f8e69f748d7ef0df7bc0b064a9b1f5c78b2..9d1a4863abd9237dbf9d1b74c78632b6a205f6bb 2020-09-29 18:42:19 +0000 to 2020-10-05 18:29:52 +0000 - Add LTO to the metadata filename hash. (rust-lang/cargo#8755) - Fix dylib+rlib with LTO. (rust-lang/cargo#8754) - Homepage doc cargo metadata (rust-lang/cargo#8744)
Hello @ehuss ! |
Stable patch releases are decided by the release team, you may want to discuss with them (they can be reached on the t-release stream on Zulip). This has been broken since at least August, and only one user mentioned it, so it wasn't a terribly high priority at the time. I'd be fine with backporting to 1.48 if the release team is planning a patch release for other reasons, but I suspect this alone probably won't justify a new release. |
A mixed dylib+rlib crate with LTO was using the wrong settings. It was using
OnlyObject
, but therlib
needs bitcode when linked with other things.Fixes #8673