-
-
Notifications
You must be signed in to change notification settings - Fork 14.8k
Should debuginfo special-case vectors? #129448
Copy link
Copy link
Open
Labels
A-debuginfoArea: Debugging information in compiled programs (DWARF, PDB, etc.)Area: Debugging information in compiled programs (DWARF, PDB, etc.)C-discussionCategory: Discussion or questions that doesn't represent real issues.Category: Discussion or questions that doesn't represent real issues.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.WG-debuggingWorking group: Bad Rust debugging experiencesWorking group: Bad Rust debugging experiences
Metadata
Metadata
Assignees
Labels
A-debuginfoArea: Debugging information in compiled programs (DWARF, PDB, etc.)Area: Debugging information in compiled programs (DWARF, PDB, etc.)C-discussionCategory: Discussion or questions that doesn't represent real issues.Category: Discussion or questions that doesn't represent real issues.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.WG-debuggingWorking group: Bad Rust debugging experiencesWorking group: Bad Rust debugging experiences
Type
Fields
Give feedbackNo fields configured for issues without a type.
In #129403 I'm seeing that using array-based SIMD types changes the debug info you get from them, and thus #128866 has in fact already changed the debuginfo you get from platform types like
__m256.Should debug-info notice the
VectorABI and emit something that doesn't get double-braced? Or does it not matter and the([1, 2])is completely fine so it's not worth changing?