Displaying 3 results from an estimated 3 matches for "form_ref_addr".
2013 Mar 09
1
[LLVMdev] Question about abstract subprograms in debug info
...t;getCUDie().
So it is not legal to use a FORM_ref4 here.
Why do we create these subprogram DIEs here? They are added to SPCU, but not inserted via insertDIE, so they are not in the MDNodeToDieMap of the CU.
Another question is how to fix this if we need to create these subprograms.
Should we use FORM_ref_addr here? FORM_ref_addr is not supported yet, I am wondering whether that will break any debugger.
Another fix seems to be copying the attributes of the origin instead of using abstract_origin.
Thanks,
Manman
2019 Sep 18
2
Remove obsolete debug info while garbage collecting
17.09.2019 3:12, David Blaikie пишет:
>
>
> On Wed, Sep 11, 2019 at 3:32 PM Alexey Lapshin via llvm-dev
> <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote:
>
> Debuginfo and linker folks, we (AccessSoftek) would like to
> suggest a proposal for removing obsolete debug info. If you find
> it useful we will be happy to work on
2019 Sep 20
3
Remove obsolete debug info while garbage collecting
...; DW_TAG_subprogram
> DW_AT_name "f1"
> 0x6e: DW_TAG_compile_unit
> DW_AT_name "b.cpp"
> 0x8d: DW_TAG_subprogram
> DW_AT_name "main"
> 0xa6: DW_TAG_inlined_subroutine
> DW_AT_abstract_origin [DW_FORM_ref_addr]
> (0x0000000000000056 "_Z2f1v")
>
> ueaueoa
> ueaoueoa
>
> Notice that the inlined_subroutine's abstract_origin uses a linker
> relocation into the debug_info section to give an absolute offset
> within the finally linked debug_info section (since the debug...