search for: dwps

...distinct CUs in the resulting DWARF. This preserves semantics as much as possible - eg: file-local functions and types (those in anonymous namespaces or declared file-static) con co-exist even if their names collide. GDB does good things with this, except with Fission. Binutils DWP produces usable DWPs from DWO files with multiple CUs 2) Cross-CU references This is where it gets trickier. LLVM produces cross-CU references (DW_FORM_ref_addr) to refer to types or functions defined in one CU used from another. This only happens with (thin or plain) LTO. LLVM's had this for a while. This helps f...

...re than creating .dwo files? > Fission as used in that sentence means .dwo files and anything beyond (.dwp files - https://gcc.gnu.org/wiki/DebugFissionDWP ). GDB warns/errors/complains if two CUs are in a single .dwo, and ignores all but the first. > > > Binutils DWP produces usable DWPs from DWO files with multiple CUs > > > > 2) Cross-CU references > > This is where it gets trickier. > > LLVM produces cross-CU references (DW_FORM_ref_addr) to refer to types > or functions defined in one CU used from another. This only happens with > (thin or plain) L...

...gt; - Allowing more than one CU in gdb? > - Emitting many little .dwo files for the cross-inlined functions' CUs? Hmm.. I guess that would make the cross-CU references impossible. (Unless we can refer to everything via signatures). > >> >> > Binutils DWP produces usable DWPs from DWO files with multiple CUs >> > >> > 2) Cross-CU references >> > This is where it gets trickier. >> > LLVM produces cross-CU references (DW_FORM_ref_addr) to refer to types or functions defined in one CU used from another. This only happens with (thin or pl...

...entially produce two CUs with the same DWO ID hash. So I was thinking there might be some need to cross-polinate the hashes of the various CUs in ThinLTO, to create 'more unique' identifiers... but I don't know exactly how it'd all look there. > Binutils DWP produces usable DWPs from DWO files with multiple CUs > > 2) Cross-CU references > This is where it gets trickier. > LLVM produces cross-CU references (DW_FORM_ref_addr) to refer to types or functions defined in one CU used from another. This only happens with (thin or plain) LTO. LLVM's had this for a...

>*nod* That's been the historic ELF+DWARF approach, but both MacOS (with dsyms+DWARF) and Windows >(COFF+CodeView+PDB) don't do it that way, and instead involve the linker to a degree. >Mostly I'm wondering if it'd be reasonable to (and if anyone would be interested in doing it) do >something more like the PDB support - fully debug-aware linking. Honestly saying I only