-
Notifications
You must be signed in to change notification settings - Fork 13k
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
[DO NOT MERGE] perf-test for #80796 #81207
Conversation
Original message: Rollup merge of rust-lang#80796 - cuviper:llvm-11.0.1, r=nikic Update to LLVM 11.0.1 This updates to a new LLVM branch, rebased on the upstream `llvmorg-11.0.1`. All our patches applied cleanly except the fortanix unwind changes, which just needed a small adjustment in cmake files. r? `@nikic` Fixes rust-lang#73722
@bors try @rust-timer queue The try commit's (master) parent should be a4cbb44. If it isn't, then please:
You do not need to reinvoke the queue command as long as the perf build hasn't yet started. |
Awaiting bors try build completion. |
⌛ Trying commit 771170b with merge 3ab423f5ac44d394fb4d47db2b4042b4a25e8b1d... |
☀️ Try build successful - checks-actions |
Queued 3ab423f5ac44d394fb4d47db2b4042b4a25e8b1d with parent a4cbb44, future comparison URL. @rustbot label: +S-waiting-on-perf |
Finished benchmarking try commit (3ab423f5ac44d394fb4d47db2b4042b4a25e8b1d): comparison url. Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. Please note that if the perf results are neutral, you should likely undo the rollup=never given below by specifying Importantly, though, if the results of this run are non-neutral do not roll this PR up -- it will mask other regressions or improvements in the roll up. @bors rollup=never |
Closing as the automated roll up perf regression tool is not working properly |
This is an automatically generated pull request (from here) to run perf tests for #80796 which merged in a rollup.
r? @ghost