mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
da7d405357
rust/src/test/codegen/generator-debug.rs

63 lines
2.4 KiB
Rust
Raw Normal View History

Add test for generator debuginfo
2020-06-18 18:17:25 -05:00
// Verify debuginfo for generators:
// - Each variant points to the file and line of its yield point
Remove artificial flag from generator variants - Literally, variants are not artificial. We have `yield` statements, upvars and inner variables in the source code. - Functionally, we don't want debuggers to suppress the variants. It contains the state of the generator, which is useful when debugging. So they shouldn't be marked artificial. - Debuggers may use artificial flags to find the active variant. In this case, marking variants artificial will make debuggers not work properly. Fixes #79009.
2021-04-30 07:02:53 -05:00
// - The discriminants are marked artificial
// - Other fields are not marked artificial
Add test for generator debuginfo
2020-06-18 18:17:25 -05:00
//
Remove redundant `ignore-tidy-linelength` annotations This is step 2 towards fixing #77548. In the codegen and codegen-units test suites, the `//` comment markers were kept in order not to affect any source locations. This is because these tests cannot be automatically `--bless`ed.
2021-04-03 06:05:11 -05:00
//
Add test for generator debuginfo
2020-06-18 18:17:25 -05:00
// compile-flags: -C debuginfo=2 --edition=2018
Generalize generator-debug test a bit Don't be so reliant on particular line ordering (though FileCheck makes this hard in general, IMO). Also disable for MSVC.
2020-06-23 18:21:53 -05:00
// ignore-msvc
Add test for generator debuginfo
2020-06-18 18:17:25 -05:00
#![feature(generators, generator_trait)]
use std::ops::Generator;
fn generator_test() -> impl Generator<Yield = i32, Return = ()> {
|| {
yield 0;
let s = String::from("foo");
yield 1;
}
}
Give up on checking filename
2020-06-23 22:19:26 -05:00
// FIXME: No way to reliably check the filename.
Add test for generator debuginfo
2020-06-18 18:17:25 -05:00
Generalize generator-debug test a bit Don't be so reliant on particular line ordering (though FileCheck makes this hard in general, IMO). Also disable for MSVC.
2020-06-23 18:21:53 -05:00
// CHECK-DAG: [[GEN_FN:!.*]] = !DINamespace(name: "generator_test"
Improve debug symbol names to avoid ambiguity and work better with MSVC's debugger 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, size>` 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).
2021-06-24 12:36:28 -05:00
// CHECK-DAG: [[GEN:!.*]] = !DICompositeType(tag: DW_TAG_structure_type, name: "{generator#0}", scope: [[GEN_FN]]
Generalize generator-debug test a bit Don't be so reliant on particular line ordering (though FileCheck makes this hard in general, IMO). Also disable for MSVC.
2020-06-23 18:21:53 -05:00
// CHECK: [[VARIANT:!.*]] = !DICompositeType(tag: DW_TAG_variant_part, scope: [[GEN_FN]],
Remove artificial flag from generator variants - Literally, variants are not artificial. We have `yield` statements, upvars and inner variables in the source code. - Functionally, we don't want debuggers to suppress the variants. It contains the state of the generator, which is useful when debugging. So they shouldn't be marked artificial. - Debuggers may use artificial flags to find the active variant. In this case, marking variants artificial will make debuggers not work properly. Fixes #79009.
2021-04-30 07:02:53 -05:00
// CHECK-NOT: flags: DIFlagArtificial
Add test for generator debuginfo
2020-06-18 18:17:25 -05:00
// CHECK-SAME: discriminator: [[DISC:![0-9]*]]
// CHECK: {{!.*}} = !DIDerivedType(tag: DW_TAG_member, name: "0", scope: [[VARIANT]],
Give up on checking filename
2020-06-23 22:19:26 -05:00
// CHECK-SAME: file: [[FILE:![0-9]*]], line: 14,
Remove artificial flag from generator variants - Literally, variants are not artificial. We have `yield` statements, upvars and inner variables in the source code. - Functionally, we don't want debuggers to suppress the variants. It contains the state of the generator, which is useful when debugging. So they shouldn't be marked artificial. - Debuggers may use artificial flags to find the active variant. In this case, marking variants artificial will make debuggers not work properly. Fixes #79009.
2021-04-30 07:02:53 -05:00
// CHECK-NOT: flags: DIFlagArtificial
// CHECK-SAME: )
Add test for generator debuginfo
2020-06-18 18:17:25 -05:00
// CHECK: {{!.*}} = !DICompositeType(tag: DW_TAG_structure_type, name: "Unresumed", scope: [[GEN]],
Remove artificial flag from generator variants - Literally, variants are not artificial. We have `yield` statements, upvars and inner variables in the source code. - Functionally, we don't want debuggers to suppress the variants. It contains the state of the generator, which is useful when debugging. So they shouldn't be marked artificial. - Debuggers may use artificial flags to find the active variant. In this case, marking variants artificial will make debuggers not work properly. Fixes #79009.
2021-04-30 07:02:53 -05:00
// CHECK-NOT: flags: DIFlagArtificial
// CHECK-SAME: )
Add test for generator debuginfo
2020-06-18 18:17:25 -05:00
// CHECK: {{!.*}} = !DIDerivedType(tag: DW_TAG_member, name: "1", scope: [[VARIANT]],
Generalize generator-debug test a bit Don't be so reliant on particular line ordering (though FileCheck makes this hard in general, IMO). Also disable for MSVC.
2020-06-23 18:21:53 -05:00
// CHECK-SAME: file: [[FILE]], line: 18,
Remove artificial flag from generator variants - Literally, variants are not artificial. We have `yield` statements, upvars and inner variables in the source code. - Functionally, we don't want debuggers to suppress the variants. It contains the state of the generator, which is useful when debugging. So they shouldn't be marked artificial. - Debuggers may use artificial flags to find the active variant. In this case, marking variants artificial will make debuggers not work properly. Fixes #79009.
2021-04-30 07:02:53 -05:00
// CHECK-NOT: flags: DIFlagArtificial
// CHECK-SAME: )
Add test for generator debuginfo
2020-06-18 18:17:25 -05:00
// CHECK: {{!.*}} = !DIDerivedType(tag: DW_TAG_member, name: "2", scope: [[VARIANT]],
Generalize generator-debug test a bit Don't be so reliant on particular line ordering (though FileCheck makes this hard in general, IMO). Also disable for MSVC.
2020-06-23 18:21:53 -05:00
// CHECK-SAME: file: [[FILE]], line: 18,
Remove artificial flag from generator variants - Literally, variants are not artificial. We have `yield` statements, upvars and inner variables in the source code. - Functionally, we don't want debuggers to suppress the variants. It contains the state of the generator, which is useful when debugging. So they shouldn't be marked artificial. - Debuggers may use artificial flags to find the active variant. In this case, marking variants artificial will make debuggers not work properly. Fixes #79009.
2021-04-30 07:02:53 -05:00
// CHECK-NOT: flags: DIFlagArtificial
// CHECK-SAME: )
Add test for generator debuginfo
2020-06-18 18:17:25 -05:00
// CHECK: {{!.*}} = !DIDerivedType(tag: DW_TAG_member, name: "3", scope: [[VARIANT]],
Generalize generator-debug test a bit Don't be so reliant on particular line ordering (though FileCheck makes this hard in general, IMO). Also disable for MSVC.
2020-06-23 18:21:53 -05:00
// CHECK-SAME: file: [[FILE]], line: 15,
Remove artificial flag from generator variants - Literally, variants are not artificial. We have `yield` statements, upvars and inner variables in the source code. - Functionally, we don't want debuggers to suppress the variants. It contains the state of the generator, which is useful when debugging. So they shouldn't be marked artificial. - Debuggers may use artificial flags to find the active variant. In this case, marking variants artificial will make debuggers not work properly. Fixes #79009.
2021-04-30 07:02:53 -05:00
// CHECK-NOT: flags: DIFlagArtificial
// CHECK-SAME: )
Add test for generator debuginfo
2020-06-18 18:17:25 -05:00
// CHECK: {{!.*}} = !DIDerivedType(tag: DW_TAG_member, name: "4", scope: [[VARIANT]],
Generalize generator-debug test a bit Don't be so reliant on particular line ordering (though FileCheck makes this hard in general, IMO). Also disable for MSVC.
2020-06-23 18:21:53 -05:00
// CHECK-SAME: file: [[FILE]], line: 17,
Remove artificial flag from generator variants - Literally, variants are not artificial. We have `yield` statements, upvars and inner variables in the source code. - Functionally, we don't want debuggers to suppress the variants. It contains the state of the generator, which is useful when debugging. So they shouldn't be marked artificial. - Debuggers may use artificial flags to find the active variant. In this case, marking variants artificial will make debuggers not work properly. Fixes #79009.
2021-04-30 07:02:53 -05:00
// CHECK-NOT: flags: DIFlagArtificial
// CHECK-SAME: )
Add test for generator debuginfo
2020-06-18 18:17:25 -05:00
// CHECK: [[S1:!.*]] = !DICompositeType(tag: DW_TAG_structure_type, name: "Suspend1", scope: [[GEN]],
Remove artificial flag from generator variants - Literally, variants are not artificial. We have `yield` statements, upvars and inner variables in the source code. - Functionally, we don't want debuggers to suppress the variants. It contains the state of the generator, which is useful when debugging. So they shouldn't be marked artificial. - Debuggers may use artificial flags to find the active variant. In this case, marking variants artificial will make debuggers not work properly. Fixes #79009.
2021-04-30 07:02:53 -05:00
// CHECK-NOT: flags: DIFlagArtificial
// CHECK-SAME: )
Add test for generator debuginfo
2020-06-18 18:17:25 -05:00
// CHECK: {{!.*}} = !DIDerivedType(tag: DW_TAG_member, name: "s", scope: [[S1]]
// CHECK-NOT: flags: DIFlagArtificial
// CHECK-SAME: )
Generalize generator-debug test a bit Don't be so reliant on particular line ordering (though FileCheck makes this hard in general, IMO). Also disable for MSVC.
2020-06-23 18:21:53 -05:00
// CHECK: [[DISC]] = !DIDerivedType(tag: DW_TAG_member, name: "__state", scope: [[GEN_FN]],
Add test for generator debuginfo
2020-06-18 18:17:25 -05:00
// CHECK-SAME: flags: DIFlagArtificial
fn main() {
let _dummy = generator_test();
}
Reference in New Issue Copy Permalink