-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
simplify layout calculations in rawvec #107167
Conversation
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
⌛ Trying commit 291a9680f195b370dc3c560a62cc8423465c743f with merge 5613aa692046f5fb9ebeddd5510baca85b56e5bb... |
☀️ Try build successful - checks-actions |
This comment has been minimized.
This comment has been minimized.
Finished benchmarking commit (5613aa692046f5fb9ebeddd5510baca85b56e5bb): comparison URL. Overall result: ❌✅ regressions and improvements - ACTION NEEDEDBenchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. While you can manually mark this PR as fit for rollup, we strongly recommend not doing so since this PR may lead to changes in compiler perf. Next Steps: If you can justify the regressions found in this try perf run, please indicate this with @bors rollup=never 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.
CyclesResultsThis 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.
|
291a968
to
a27b347
Compare
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
⌛ Trying commit a27b3474ed6727423d1a6ed8e9724ed15ded87a7 with merge 3c1f86b6ba4eb0c6d1d29b6cdd1f475c605dbc5d... |
☀️ Try build successful - checks-actions |
This comment has been minimized.
This comment has been minimized.
Finished benchmarking commit (3c1f86b6ba4eb0c6d1d29b6cdd1f475c605dbc5d): comparison URL. Overall result: ✅ improvements - no action neededBenchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. While you can manually mark this PR as fit for rollup, we strongly recommend not doing so since this PR may lead to changes in compiler perf. @bors rollup=never 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.
CyclesResultsThis 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.
|
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
⌛ Trying commit 7c3da9ae62a73d5460b9ca59eb04fdf581313737 with merge be7d0536f688ba266e7d2d3e9ad9dd2223e7f2a2... |
☀️ Try build successful - checks-actions |
The job Click to see the possible cause of the failure (guessed by this bot)
|
Hm, I've seen that failure before. At first glance it looks kinda like some kind of miscomputation in In any case, I don't think it has anything to do with the changes in this PR. |
retrying per comment above @bors r=thomcc rollup=iffy |
💡 This pull request was already approved, no need to approve it again.
|
⌛ Testing commit 6fcf175 with merge 54b261ab13fc0fa54a048a3bfac3524b76530ce1... |
💔 Test failed - checks-actions |
I opened the above issue to look in to this. I can reproduce on master without this PR so I'm still fairly confident this is not the cause. Although it does seem to be triggering CI for some reason. |
The job Click to see the possible cause of the failure (guessed by this bot)
|
☀️ Test successful - checks-actions |
Finished benchmarking commit (8dabf5d): comparison URL. Overall result: ❌✅ regressions and improvements - ACTION NEEDEDNext Steps: If you can justify the regressions found in this perf run, please indicate this with @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.
CyclesResultsThis 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.
|
Improvements greatly exceed regressions here. @rustbot label: +perf-regression-triaged |
The use of
Layout::array
was introduced in #83706 which lead to a perf regression.This PR basically reverts that change since rust currently only supports stride == size types, but to be on the safe side it leaves a const-assert there to make sure this gets caught if those assumptions ever change.