-
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
Erase late-bound regions before computing vtable debuginfo name. #90050
Erase late-bound regions before computing vtable debuginfo name. #90050
Conversation
This comment has been minimized.
This comment has been minimized.
0e6c7a2
to
bf39d86
Compare
@bors r+ |
📌 Commit bf39d86 has been approved by |
Co-authored-by: r00ster <[email protected]>
@bors r+ |
📌 Commit 5929cf0 has been approved by |
@bors p=1 Fixes stable-to-beta regression. |
☀️ Test successful - checks-actions |
Finished benchmarking commit (3d71e74): 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`
Fixes #90019.
The
msvc_enum_fallback()
for computing enum type names needs to access the memory layout of niche enums in order to determine the type name.compute_debuginfo_vtable_name()
did not properly erase regions before computing type names which made memory layout computation ICE when encountering un-erased regions.r? @wesleywiser