mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
b22bc276f8
rust/tests/debuginfo/generator-objects.rs

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

99 lines
3.2 KiB
Rust
Raw Normal View History

Update the minimum external LLVM to 8 LLVM 8 was released on March 20, 2019, over a year ago.
2020-04-14 14:10:58 -05:00
// Require a gdb that can read DW_TAG_variant_part.
Describe generator variants in debuginfo
2019-04-12 19:03:03 -05:00
// min-gdb-version: 8.2
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
// LLDB without native Rust support cannot read DW_TAG_variant_part,
// so it prints nothing for generators. But those tests are kept to
// ensure that LLDB won't crash at least (like #57822).
Describe generator variants in debuginfo
2019-04-12 19:03:03 -05:00
// compile-flags:-g
// === GDB TESTS ===================================================================================
// gdb-command:run
// gdb-command:print b
debuginfo: Make sure that type names for closure and generator environments are unique in debuginfo. Before this change, closure/generator environments coming from different instantiations of the same generic function were all assigned the same name even though they were distinct types with potentially different data layout. Now we append the generic arguments of the originating function to the type name. This commit also emits '{closure_env#0}' as the name of these types in order to disambiguate them from the accompanying closure function '{closure#0}'. Previously both were assigned the same name.
2022-01-19 10:56:53 -06:00
// gdb-check:$1 = generator_objects::main::{generator_env#0}::Unresumed{_ref__a: 0x[...]}
Describe generator variants in debuginfo
2019-04-12 19:03:03 -05:00
// gdb-command:continue
// gdb-command:print b
debuginfo: Make sure that type names for closure and generator environments are unique in debuginfo. Before this change, closure/generator environments coming from different instantiations of the same generic function were all assigned the same name even though they were distinct types with potentially different data layout. Now we append the generic arguments of the originating function to the type name. This commit also emits '{closure_env#0}' as the name of these types in order to disambiguate them from the accompanying closure function '{closure#0}'. Previously both were assigned the same name.
2022-01-19 10:56:53 -06:00
// gdb-check:$2 = generator_objects::main::{generator_env#0}::Suspend0{c: 6, d: 7, _ref__a: 0x[...]}
Describe generator variants in debuginfo
2019-04-12 19:03:03 -05:00
// gdb-command:continue
// gdb-command:print b
debuginfo: Make sure that type names for closure and generator environments are unique in debuginfo. Before this change, closure/generator environments coming from different instantiations of the same generic function were all assigned the same name even though they were distinct types with potentially different data layout. Now we append the generic arguments of the originating function to the type name. This commit also emits '{closure_env#0}' as the name of these types in order to disambiguate them from the accompanying closure function '{closure#0}'. Previously both were assigned the same name.
2022-01-19 10:56:53 -06:00
// gdb-check:$3 = generator_objects::main::{generator_env#0}::Suspend1{c: 7, d: 8, _ref__a: 0x[...]}
Describe generator variants in debuginfo
2019-04-12 19:03:03 -05:00
// gdb-command:continue
// gdb-command:print b
debuginfo: Make sure that type names for closure and generator environments are unique in debuginfo. Before this change, closure/generator environments coming from different instantiations of the same generic function were all assigned the same name even though they were distinct types with potentially different data layout. Now we append the generic arguments of the originating function to the type name. This commit also emits '{closure_env#0}' as the name of these types in order to disambiguate them from the accompanying closure function '{closure#0}'. Previously both were assigned the same name.
2022-01-19 10:56:53 -06:00
// gdb-check:$4 = generator_objects::main::{generator_env#0}::Returned{_ref__a: 0x[...]}
Describe generator variants in debuginfo
2019-04-12 19:03:03 -05:00
// === LLDB TESTS ==================================================================================
// lldb-command:run
// lldb-command:print b
debuginfo: Make sure that type names for closure and generator environments are unique in debuginfo. Before this change, closure/generator environments coming from different instantiations of the same generic function were all assigned the same name even though they were distinct types with potentially different data layout. Now we append the generic arguments of the originating function to the type name. This commit also emits '{closure_env#0}' as the name of these types in order to disambiguate them from the accompanying closure function '{closure#0}'. Previously both were assigned the same name.
2022-01-19 10:56:53 -06:00
// lldbg-check:(generator_objects::main::{generator_env#0}) $0 =
Describe generator variants in debuginfo
2019-04-12 19:03:03 -05:00
// lldb-command:continue
// lldb-command:print b
debuginfo: Make sure that type names for closure and generator environments are unique in debuginfo. Before this change, closure/generator environments coming from different instantiations of the same generic function were all assigned the same name even though they were distinct types with potentially different data layout. Now we append the generic arguments of the originating function to the type name. This commit also emits '{closure_env#0}' as the name of these types in order to disambiguate them from the accompanying closure function '{closure#0}'. Previously both were assigned the same name.
2022-01-19 10:56:53 -06:00
// lldbg-check:(generator_objects::main::{generator_env#0}) $1 =
Describe generator variants in debuginfo
2019-04-12 19:03:03 -05:00
// lldb-command:continue
// lldb-command:print b
debuginfo: Make sure that type names for closure and generator environments are unique in debuginfo. Before this change, closure/generator environments coming from different instantiations of the same generic function were all assigned the same name even though they were distinct types with potentially different data layout. Now we append the generic arguments of the originating function to the type name. This commit also emits '{closure_env#0}' as the name of these types in order to disambiguate them from the accompanying closure function '{closure#0}'. Previously both were assigned the same name.
2022-01-19 10:56:53 -06:00
// lldbg-check:(generator_objects::main::{generator_env#0}) $2 =
Describe generator variants in debuginfo
2019-04-12 19:03:03 -05:00
// lldb-command:continue
// lldb-command:print b
debuginfo: Make sure that type names for closure and generator environments are unique in debuginfo. Before this change, closure/generator environments coming from different instantiations of the same generic function were all assigned the same name even though they were distinct types with potentially different data layout. Now we append the generic arguments of the originating function to the type name. This commit also emits '{closure_env#0}' as the name of these types in order to disambiguate them from the accompanying closure function '{closure#0}'. Previously both were assigned the same name.
2022-01-19 10:56:53 -06:00
// lldbg-check:(generator_objects::main::{generator_env#0}) $3 =
Describe generator variants in debuginfo
2019-04-12 19:03:03 -05:00
debuginfo: change cpp-like naming for generator environments so that NatVis works for them
2022-03-03 05:10:02 -06:00
// === CDB TESTS ===================================================================================
// cdb-command: g
// cdb-command: dx b
Use enum2<_> instead of enum<_> for Cpp-like debuginfo enum type names. And add more comments about niche tag enum encoding.
2022-07-07 08:01:43 -05:00
// cdb-check: b : Unresumed [Type: enum2$<generator_objects::main::generator_env$0>]
debuginfo: Refactor debuginfo generation for types -- Make generator-objects test case architecture independent.
2022-03-15 05:45:51 -05:00
// cdb-check: [+0x[...]] _ref__a : 0x[...] : 5 [Type: int *]
debuginfo: change cpp-like naming for generator environments so that NatVis works for them
2022-03-03 05:10:02 -06:00
// cdb-command: g
// cdb-command: dx b
Use enum2<_> instead of enum<_> for Cpp-like debuginfo enum type names. And add more comments about niche tag enum encoding.
2022-07-07 08:01:43 -05:00
// cdb-check: b : Suspend0 [Type: enum2$<generator_objects::main::generator_env$0>]
debuginfo: Refactor debuginfo generation for types -- Make generator-objects test case architecture independent.
2022-03-15 05:45:51 -05:00
// cdb-check: [+0x[...]] c : 6 [Type: int]
// cdb-check: [+0x[...]] d : 7 [Type: int]
// cdb-check: [+0x[...]] _ref__a : 0x[...] : 5 [Type: int *]
debuginfo: change cpp-like naming for generator environments so that NatVis works for them
2022-03-03 05:10:02 -06:00
// cdb-command: g
// cdb-command: dx b
Use enum2<_> instead of enum<_> for Cpp-like debuginfo enum type names. And add more comments about niche tag enum encoding.
2022-07-07 08:01:43 -05:00
// cdb-check: b : Suspend1 [Type: enum2$<generator_objects::main::generator_env$0>]
debuginfo: Refactor debuginfo generation for types -- Make generator-objects test case architecture independent.
2022-03-15 05:45:51 -05:00
// cdb-check: [+0x[...]] c : 7 [Type: int]
// cdb-check: [+0x[...]] d : 8 [Type: int]
// cdb-check: [+0x[...]] _ref__a : 0x[...] : 6 [Type: int *]
debuginfo: change cpp-like naming for generator environments so that NatVis works for them
2022-03-03 05:10:02 -06:00
// cdb-command: g
// cdb-command: dx b
Use enum2<_> instead of enum<_> for Cpp-like debuginfo enum type names. And add more comments about niche tag enum encoding.
2022-07-07 08:01:43 -05:00
// cdb-check: b : Returned [Type: enum2$<generator_objects::main::generator_env$0>]
debuginfo: Refactor debuginfo generation for types -- Make generator-objects test case architecture independent.
2022-03-15 05:45:51 -05:00
// cdb-check: [+0x[...]] _ref__a : 0x[...] : 6 [Type: int *]
debuginfo: change cpp-like naming for generator environments so that NatVis works for them
2022-03-03 05:10:02 -06:00
Describe generator variants in debuginfo
2019-04-12 19:03:03 -05:00
#![feature(omit_gdb_pretty_printer_section, generators, generator_trait)]
#![omit_gdb_pretty_printer_section]
use std::ops::Generator;
use std::pin::Pin;
fn main() {
let mut a = 5;
let mut b = || {
let mut c = 6;
let mut d = 7;
yield;
a += 1;
c += 1;
d += 1;
yield;
println!("{} {} {}", a, c, d);
};
_zzz(); // #break
Add a resume type parameter to `Generator`
2020-01-25 13:03:10 -06:00
Pin::new(&mut b).resume(());
Describe generator variants in debuginfo
2019-04-12 19:03:03 -05:00
_zzz(); // #break
Add a resume type parameter to `Generator`
2020-01-25 13:03:10 -06:00
Pin::new(&mut b).resume(());
Describe generator variants in debuginfo
2019-04-12 19:03:03 -05:00
_zzz(); // #break
Add a resume type parameter to `Generator`
2020-01-25 13:03:10 -06:00
Pin::new(&mut b).resume(());
Describe generator variants in debuginfo
2019-04-12 19:03:03 -05:00
_zzz(); // #break
}
debuginfo: Refactor debuginfo generation for types -- Make generator-objects test case architecture independent.
2022-03-15 05:45:51 -05:00
#[inline(never)]
debuginfo: Make sure that type names for closure and generator environments are unique in debuginfo. Before this change, closure/generator environments coming from different instantiations of the same generic function were all assigned the same name even though they were distinct types with potentially different data layout. Now we append the generic arguments of the originating function to the type name. This commit also emits '{closure_env#0}' as the name of these types in order to disambiguate them from the accompanying closure function '{closure#0}'. Previously both were assigned the same name.
2022-01-19 10:56:53 -06:00
fn _zzz() {
()
}
Reference in New Issue Copy Permalink