rust/compiler/rustc_codegen_ssa/src/debuginfo, branch 1.55.0

Add self-profiling to debuginfo name generation

2021-07-15T10:21:15+00:00

[debuginfo] Make use of spaces and separators in debuginfo names more uniform.

2021-07-15T10:21:05+00:00

[debuginfo] Emit associated type bindings in trait object type names.

2021-07-15T08:40:25+00:00

Handle non-integer const generic parameters in debuginfo type names.

2021-07-14T13:55:03+00:00

Refactor `msvc_enum_fallbck()` a bit

2021-07-03T00:38:37+00:00

Show the variant name for univariant enums

2021-07-03T00:16:37+00:00

Previously, only the fields would be displayed with no indication of the variant name. If you already knew the enum was univariant, this was ok but if the enum was univariant because of layout, for example, a `Result` then it could be very confusing which variant was the active one.

Update cdb tests for expected output

2021-07-01T18:26:20+00:00

Also an fix issue with tuple type names where we can't cast to them in natvis (required by the visualizer for `HashMap`) because of peculiarities with the natvis expression evaluator.

Improve debug symbol names to avoid ambiguity and work better with MSVC's debugger

2021-06-30T18:10:29+00:00

There are several cases where names of types and functions in the debug info are either ambiguous, or not helpful, such as including ambiguous placeholders (e.g., `{{impl}}`, `{{closure}}` or `dyn _'`) or dropping qualifications (e.g., for dynamic types). Instead, each debug symbol name should be unique and useful: * Include disambiguators for anonymous `DefPathDataName` (closures and generators), and unify their formatting when used as a path-qualifier vs item being qualified. * Qualify the principal trait for dynamic types. * If there is no principal trait for a dynamic type, emit all other traits instead. * Respect the `qualified` argument when emitting ref and pointer types. * For implementations, emit the disambiguator. * Print const generics when emitting generic parameters or arguments. Additionally, when targeting MSVC, its debugger treats many command arguments as C++ expressions, even when the argument is defined to be a symbol name. As such names in the debug info need to be more C++-like to be parsed correctly: * Avoid characters with special meaning (`#`, `[`, `"`, `+`). * Never start a name with `<` or `{` as this is treated as an operator. * `>>` is always treated as a right-shift, even when parsing generic arguments (so add a space to avoid this). * Emit function declarations using C/C++ style syntax (e.g., leading return type). * Emit arrays as a synthetic `array$` type. * Include a `$` in all synthetic types as this is a legal character for C++, but not Rust (thus we avoid collisions with user types).

Respond to review feedback

2021-06-02T14:23:12+00:00

Change the type name from `_enum<..>` to `enum$<..>`

2021-06-02T14:23:12+00:00

This makes the type name inline with the proposed standard in #85269.