-
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
rustc_session: default to -Z plt=yes on non-x86_64 #109982
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @nikic (or someone else) soon. Please see the contribution instructions for more information. Namely, in order to ensure the minimum review times lag, PR authors and assigned reviewers should ensure that the review label (
|
@@ -978,7 +978,7 @@ impl Session { | |||
pub fn needs_plt(&self) -> bool { | |||
// Check if the current target usually needs PLT to be enabled. | |||
// The user can use the command line flag to override it. | |||
let needs_plt = self.target.needs_plt; | |||
let needs_plt = self.target.arch != "x86_64"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should still be based on a target property. Just inverted from needs_plt
to no_plt_by_default
or something.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I did that, but I realized as I did it that this might invalidate existing target json files. Is that something I need to worry about?
(I'm also only about 70% sure I did this right, so please give it careful scrutiny)
This comment has been minimized.
This comment has been minimized.
@durin42 any updates on this? thanks |
I'll get back to it - I've been out of the office for most of May, but should get back to this in early June. If someone else wants to take this over, I won't be offended, just have had a busy month. :) |
d4834e8
to
0d21728
Compare
These commits modify compiler targets. |
@rustbot review |
@bors r+ rollup=never |
📌 Commit 0d21728597d2f6bbda7d56cbb55e0848917c04b8 has been approved by It is now in the queue for this repository. |
⌛ Testing commit 0d21728597d2f6bbda7d56cbb55e0848917c04b8 with merge c7b76ef7e61b11a84a7eff0556fe84e383763eaa... |
This comment has been minimized.
This comment has been minimized.
💔 Test failed - checks-actions |
Per the discussion in rust-lang#106380 plt=no isn't a great default, and rust-lang/compiler-team#581 decided that the default should be PLT=yes for everything except x86_64. Not everyone agrees about the x86_64 part of this change, but this at least is an improvement in the state of things without changing the x86_64 situation, so I've attempted making this change in the name of not letting the perfect be the enemy of the good.
0d21728
to
34d0cff
Compare
@bors r+ |
☀️ Test successful - checks-actions |
Finished benchmarking commit (c79d6be): comparison URL. Overall result: ✅ improvements - no action needed@rustbot label: -perf-regression Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesThis benchmark run did not return any relevant results for this metric. Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 661.369s -> 661.671s (0.05%) |
Per the discussion in #106380 plt=no isn't a great default, and rust-lang/compiler-team#581 decided that the default should be PLT=yes for everything except x86_64. Not everyone agrees about the x86_64 part of this change, but this at least is an improvement in the state of things without changing the x86_64 situation, so I've attempted making this change in the name of not letting the perfect be the enemy of the good.
Please let me know if I've messed this up somehow - I'm not wholly confident I got this right.
r? @nikic