-
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
Tweak SubstFolder
implementation
#99600
Conversation
(rust-highfive has picked a reviewer for you, use r? to override) |
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 33f85f96a8d0019428bacb82c60544b45576f7e0 with merge 014f8963d55c62c9ab3088f4dfebf2d010b8c310... |
☀️ Try build successful - checks-actions |
Queued 014f8963d55c62c9ab3088f4dfebf2d010b8c310 with parent 41419e7, future comparison URL. |
Bug reporting macro `span_bug!` generates quite a bit of code, we don't expect to execute. Outline it into a separate function.
@bors try |
⌛ Trying commit e497fb1 with merge a4e2471b02d6ee792029881218204c4f6ef4e1d4... |
Finished benchmarking commit (014f8963d55c62c9ab3088f4dfebf2d010b8c310): comparison url. Instruction count
Max RSS (memory usage)Results
CyclesResults
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. Benchmarking 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 Footnotes |
☀️ Try build successful - checks-actions |
@rust-timer build a4e2471b02d6ee792029881218204c4f6ef4e1d4 |
Queued a4e2471b02d6ee792029881218204c4f6ef4e1d4 with parent 41419e7, future comparison URL. |
Finished benchmarking commit (a4e2471b02d6ee792029881218204c4f6ef4e1d4): comparison url. Instruction count
Max RSS (memory usage)This benchmark run did not return any relevant results for this metric. CyclesResults
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. Benchmarking 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 Footnotes |
@bors r+ |
☀️ Test successful - checks-actions |
Finished benchmarking commit (2f320a2): comparison url. Instruction count
Max RSS (memory usage)Results
CyclesThis benchmark run did not return any relevant results for this metric. If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression Footnotes |
No description provided.