-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
update stdsimd #59556
update stdsimd #59556
Conversation
(rust_highfive has picked a reviewer for you, use r? to override) |
|
oh sorry, LGTM! This update should go smoothly since rust-lang/rust is tracking stdsimd very closely lately. |
So should I do r=gnzlbg then or how do you usually handle this? |
Looks like there is precedence for that, so let's do that. @bors r=gnzlbg |
📌 Commit d8a6b63 has been approved by |
update stdsimd Cc @gnzlbg
update stdsimd Cc @gnzlbg
update stdsimd Cc @gnzlbg
update stdsimd Cc @gnzlbg
Rollup of 8 pull requests Successful merges: - #59470 (Document std::fs::File close behavior ignoring errors) - #59555 (update miri) - #59556 (update stdsimd) - #59596 (Forward formatter settings to bounds of `Range<T>` in `fmt::Debug` impl) - #59639 (Never return uninhabited values at all) - #59671 (Make some of lexer's API private) - #59685 (Add description for -Os and -Oz in rustc.1) - #59686 (Temporarily disable stack probing for gnux32.) Failed merges: r? @ghost
Why is bors testing this and #59671? It is already merged. |
Uh... bors seems very confused. @bors r- retry Cc @rust-lang/infra |
Heh, weird things happen when bors is redeployed... |
Cc @gnzlbg