-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Allow for opting out of ThinLTO and clean up LTO related cli flag handling. #53950
Conversation
Looks good to me! Perhaps someone from @rust-lang/compiler can kick off an FCP to merge? |
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
@rfcbot fcp merge |
Team member @cramertj has proposed to merge this. The next step is review by the rest of the tagged teams:
No concerns currently listed. Once a majority of reviewers approve (and none object), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up! See this document for info about what commands tagged team members can give me. |
8c0c29b
to
24093a6
Compare
Ping @rust-lang/compiler: It would be great if we could get this merged before the beta cut-off (if it's not too late already). Please tick off your box if you haven't already! ❤️ |
We have approximately 2 days left before beta cutoff, though we might delay slightly to make sure edition-related components make it in. So far though looks like we're on schedule for Tuesday. |
🔔 This is now entering its final comment period, as per the review above. 🔔 |
OK, everybody signed off but since the FCP will run for another week, I guess we'll have to do a beta backport? |
@bors: r+ I'm pretty confident in this, but if a concern is raised during FCP I volunteer to be on the hook to revert it from beta |
📌 Commit 24093a6 has been approved by |
⌛ Testing commit 24093a6 with merge 502e750e7f02fe048dcf9ef51e726d24c1f74c24... |
💔 Test failed - status-travis |
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
@bors: retry we should have longer than 50m to do a build... |
…excrichton Allow for opting out of ThinLTO and clean up LTO related cli flag handling. It turns out that there currently is no way to explicitly disable ThinLTO (except for the nightly-only `-Zthinlto` flag). This PR extends `-C lto` to take `yes` and `no` in addition to `thin` and `fat`. It should be backwards compatible. It also cleans up how LTO mode selection is handled. Note that merging the PR in the current state would make the new values for `-C lto` available on the stable channel. I think that would be fine but maybe some team should vote on it.
Rollup of 11 pull requests Successful merges: - #53371 (Do not emit E0277 on incorrect tuple destructured binding) - #53829 (Add rustc SHA to released DWARF debuginfo) - #53950 (Allow for opting out of ThinLTO and clean up LTO related cli flag handling.) - #53976 (Replace unwrap calls in example by expect) - #54070 (Add Error::description soft-deprecation to RELEASES) - #54076 (miri loop detector hashing) - #54119 (Add some unit tests for find_best_match_for_name) - #54147 (Add a test that tries to modify static memory at compile-time) - #54150 (Updated 1.29 release notes with --document-private-items flag) - #54163 (Update stage 0 to latest beta) - #54170 (COMPILER_TESTS.md has been moved)
It turns out that there currently is no way to explicitly disable ThinLTO (except for the nightly-only
-Zthinlto
flag). This PR extends-C lto
to takeyes
andno
in addition tothin
andfat
. It should be backwards compatible.It also cleans up how LTO mode selection is handled.
Note that merging the PR in the current state would make the new values for
-C lto
available on the stable channel. I think that would be fine but maybe some team should vote on it.r? @alexcrichton