search for: d70833

...ter operation. >> >> Both of these two branches have some common implementation to define new >> operations (Dwarf and IR). (D70642, D70643, D69999, D69886). >> First branch has additional patches (D70260, 70384, D70385, D70419). >> Second branch has additional patch ( D70833). >> >> Let me try to comment on points raised by you. >> - Branch 2, (patch D70833) handles cases when temporaries (not existing >> variables) are optimized out. >> - In patch D70385, I have included test points to display that multi >> layered pointers are work...

Hi folks, I am pushing a PoC patch https://reviews.llvm.org/D70833 for review which includes the case when temporary is promoted. For such cases it generates IR as call void @llvm.dbg.derefval(metadata i32 3, metadata !25, metadata !DIExpression(DW_OP_LLVM_explicit_pointer, DW_OP_LLVM_arg0)), !dbg !32 And llvm-darfdump output looks like ------------- 0x00000...

...ng 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 branch has additional patches (D70260, 70384, D70385, D70419). Second branch has additional patch ( D70833). Let me try to comment on points raised by you. - Branch 2, (patch D70833) handles cases when temporaries (not existing variables) are optimized out. - In patch D70385, I have included test points to display that multi layered pointers are working (llvm/test/DebugInfo/dwarfdump-implicit_pointer_m...

...have some common implementation to define >>>>>>> new operations (Dwarf and IR). (D70642, D70643, D69999, D69886). >>>>>>> First branch has additional patches (D70260, 70384, D70385, D70419). >>>>>>> Second branch has additional patch ( D70833). >>>>>>> >>>>>>> Let me try to comment on points raised by you. >>>>>>> - Branch 2, (patch D70833) handles cases when temporaries (not >>>>>>> existing variables) are optimized out. >>>>>>> - I...

> 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