-
Notifications
You must be signed in to change notification settings - Fork 14.1k
Don't treat asserts as a call in cross-crate inlining #117192
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
base: main
Are you sure you want to change the base?
Conversation
|
Some changes occurred to MIR optimizations cc @rust-lang/wg-mir-opt |
|
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
Don't treat asserts as a call in cross-crate inlining r? `@ghost`
|
☀️ Try build successful - checks-actions |
This comment has been minimized.
This comment has been minimized.
|
Finished benchmarking commit (4729728): 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.
CyclesThis benchmark run did not return any relevant results for this metric. Binary sizeResultsThis 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.
Bootstrap: missing data |
|
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
Don't treat asserts as a call in cross-crate inlining r? `@ghost`
|
☀️ Try build successful - checks-actions |
This comment has been minimized.
This comment has been minimized.
|
Finished benchmarking commit (4ddfadb): 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.
Binary sizeResultsThis 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.
Bootstrap: missing data |
|
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
Don't treat asserts as a call in cross-crate inlining r? `@ghost`
|
☀️ Try build successful - checks-actions |
|
The try build finished after I force-pushed the change. test-various passes locally with the latest push. @bors r=scottmcm |
Don't treat asserts as a call in cross-crate inlining Making functions with calls in their bodies automatically cross-crate-inlinable tends to tank incremental build times. Though assert terminators are _like_ calls, they don't exhibit the same behavior.
This comment has been minimized.
This comment has been minimized.
|
💔 Test failed - checks-actions |
|
@bors try jobs=i686-msvc-1 |
This comment has been minimized.
This comment has been minimized.
Don't treat asserts as a call in cross-crate inlining try-job: i686-msvc-1
5132920 to
266aa1b
Compare
This comment has been minimized.
This comment has been minimized.
|
💔 Test for 582ce2f failed: CI. Failed jobs:
|
|
@bors try jobs=i686-msvc-1 |
This comment has been minimized.
This comment has been minimized.
Don't treat asserts as a call in cross-crate inlining try-job: i686-msvc-1
56b9cb2 to
31e94ff
Compare
|
@bors try cancel |
|
Try build cancelled. Cancelled workflows: |
|
@bors try jobs=i686-msvc-1,i686-msvc-2,x86_64-msvc-1,x86_64-msvc-2 |
This comment has been minimized.
This comment has been minimized.
Don't treat asserts as a call in cross-crate inlining try-job: i686-msvc-1 try-job: i686-msvc-2 try-job: x86_64-msvc-1 try-job: x86_64-msvc-2
This comment has been minimized.
This comment has been minimized.
|
💔 Test for 40a2216 failed: CI. Failed jobs:
|
31e94ff to
daa77e6
Compare
|
#148849 Is the fix for the Windows tests I've been fighting with. |
Making functions with calls in their bodies automatically cross-crate-inlinable tends to tank incremental build times. Though assert terminators are like calls, they don't exhibit the same behavior.