-
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
Fix wrong niche calculation when 2+ niches are placed at the start #90040
Conversation
(rust-highfive has picked a reviewer for you, use r? to override) |
@bors r+ p=5 |
📌 Commit 7dbd5bb has been approved by |
Accepting for beta, as the fix lgtm, is trivial and fixes a soundness problem. cc @rust-lang/compiler |
(Posted in the issue as well for redundancy) For the record, while I may have seen #87794 (comment) I do not recall ever reviewing the change it links to (52f4be9), which is where the bug was introduced (I was tipped off by the closures which did not exist in the version of that PR I reviewed). |
☀️ Test successful - checks-actions |
lgtm, sorry for messing up the subtraction. |
Finished benchmarking commit (d45ed75): comparison url. Summary: This benchmark run did not return any relevant changes. If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression |
…ulacrum [beta] backports * Don't emit a warning for empty rmeta files. rust-lang#90072 * Erase late-bound regions before computing vtable debuginfo name. rust-lang#90050 * Fix wrong niche calculation when 2+ niches are placed at the start rust-lang#90040 * Revert rust-lang#86011 to fix an incorrect bound check rust-lang#90025 * Fix macro_rules! duplication when reexported in the same module rust-lang#89867 * Bump cargo to include rust-lang/cargo#9979 - Fix fetching git repos after a force push. r? `@Mark-Simulacrum`
When the niche is at the start, existing code incorrectly uses 1 instead of count for subtraction.
Fix #90038
@rustbot label: T-compiler