search for: dw_op_explicit_point

...uild.d/david.cc") DW_AT_call_line (10) DW_AT_call_column (0x03) 0x00000088: DW_TAG_formal_parameter DW_AT_location (indexed (0x0) loclist = 0x00000010: [0x00000000004004c6, 0x00000000004004d4): DW_OP_explicit_pointer, DW_OP_lit3) DW_AT_abstract_origin (0x00000055 "p") ------------ Please note that DW_OP_explicit_pointer denotes that following value represents de-referenced value of optimized out pointer. With necessary changes in LLDB debugger this dwarf info can help to d...

...peration. >> >> 2. When a temporary variable is optimized out and that variable is used >> to get de-referenced value of another reference variable (AFAIK it can not >> be reproduced with pointers) >> Such cases are being addressed using new Dwarf expression >> DW_OP_explicit_pointer as de-referenced value can be displayed explicitly >> (in place). In LLVM IR, we represent it using dbg.derefval and >> DW_OP_LLVM_explicit_pointer operation. >> >> Both of these two branches have some common implementation to define new >> operations (Dwarf and IR)....

...inter or reference) and DW_OP_LLVM_implicit_pointer operation. 2. When a temporary variable is optimized out and that variable is used to get de-referenced value of another reference variable (AFAIK it can not be reproduced with pointers) Such cases are being addressed using new Dwarf expression DW_OP_explicit_pointer as de-referenced value can be displayed explicitly (in place). In LLVM IR, we represent it using dbg.derefval and DW_OP_LLVM_explicit_pointer operation. Both of these two branches have some common implementation to define new operations (Dwarf and IR). (D70642, D70643, D69999, D69886). First bra...

> I don't have a strong opinion on representation. I can see how having a dedicated instruction to model implicit pointers would aid readability & be simpler to document/grok, but perhaps in the future we'll want to support other operations that refer to variable > DIEs. In the short term migrating to an extended dbg.value representation might take more work. Alok, wdyt? Below

...at variable is >>>>>>> used to get de-referenced value of another reference variable (AFAIK it can >>>>>>> not be reproduced with pointers) >>>>>>> Such cases are being addressed using new Dwarf expression >>>>>>> DW_OP_explicit_pointer as de-referenced value can be displayed explicitly >>>>>>> (in place). In LLVM IR, we represent it using dbg.derefval and >>>>>>> DW_OP_LLVM_explicit_pointer operation. >>>>>>> >>>>>>> Both of these two branches h...