-
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
Update llvm-project #98567
Update llvm-project #98567
Conversation
r? @cuviper (rust-highfive has picked a reviewer for you, use r? to override) |
|
duplicate with #98285 ? |
Kinda, that one doesn't contain the recent commit from yesterday that fixes the AVR bug I've linked 😅 (since it uses llvm-project from two days ago) I guess I'll just rebase my PR after #98285 gets merged. |
☔ The latest upstream changes (presumably #98285) made this pull request unmergeable. Please resolve the merge conflicts. |
Ready! |
@bors r+ |
📌 Commit dafe7a17847dfb287430155ab0c6be84da0b556b has been approved by |
As this hasn't been merged yet, would you mind updating this PR to the latest commit? I've pushed two more backports. |
Sure, I’ll take a look in two hours or so 🙂 |
kk, done! |
Thanks! @bors r+ rollup=never |
📌 Commit d61e4a4 has been approved by |
☀️ Test successful - checks-actions |
Finished benchmarking commit (0aef720): 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. Next Steps: If you can justify the regressions found in this perf run, please indicate this with @rustbot label: +perf-regression Footnotes |
Perf result seems to be noise, it seems to be the opposite of the results on the previous commit: https://perf.rust-lang.org/compare.html?start=f342bea9d19f14616c6559312552e6d0ee529cfd&end=5b8cf49c51833ee5d27ae2e8e179337dbb9f14d7&stat=instructions:u |
Beta nominating as fix for the P-critical miscompile in #98568. The update also includes a fix for an AVR-only miscompile (#98167), as well as an assertion failure (#98076). Submodule diff: rust-lang/llvm-project@d1ddc34...8b6b501 |
@nikic is it a problem if we backport by rolling forward to the latest commit here on beta? (rust-lang/llvm-project@c9e2e89...8b6b501) Otherwise can create a targeted backport with a helper branch, but want to make sure there's no accidental mistakes missing a dependency on a previous commit here. |
@Mark-Simulacrum I think we need a separate backport branch here, because the LLVM fork has been rebased in the meantime, and I'm not confident that it will build on beta (specifically FreeBSD). And no, I don't think there are any relevant dependency commits. |
OK, sounds good. I'll look into doing that. |
This cherry picks: * c9676870a8f378940ec446c4184254f361feabe6 * f14a034634ac7ddc314008e39d62af6ceae0166a * 3317cfea1b72c0861c9e4e9f5eba5713fd19e7f7 * 8b6b5014fdad3a750f7242a6bfdcad83619498d4
Included in #99098, branch rustc/14.0-2022-07-09. |
…ulacrum [beta] backport rollup * Return a FxIndexSet in is_late_bound query. rust-lang#98959 * rustdoc: filter '_ lifetimes from ty::PolyTraitRef rust-lang#98727 * don't succeed evaluate_obligation query if new opaque types were registered rust-lang#98614 * Update llvm-project rust-lang#98567 There's a few more as-yet-unapproved/unmerged PRs that'll land later, but creating a partial rollup for now so that we can include at least some PRs in the first crater run. r? `@Mark-Simulacrum`
Dropping regression label, agree that the results are likely noise. See #98925 (comment) for some graphs. |
Newest rustc contains an important bugfix to AVR's code generator (rust-lang/rust#98567). Ref: Rahix/avr-hal-template#9
Closes #98167 🙂