search for: splitdwarf

Hi DebugInfo folks, I have a question on using fsplit-dwarf-inlining option: "-fsplit-dwarf-inlining, -fno-split-dwarf-inlining Provide minimal debug info in the object/executable to facilitate online symbolication/stack traces in the absence of .dwo/.dwp files when using Split DWARF" i.e. it puts some debug info into compilation unit from First partition(with Skeleton unit). At

...;> in the iterative development cycle, only in final releases - well, >>>>> maybe their situation is more "neutral" - not a major pain point in >>>>> any case I'd guess. >>>>> >>>>> >>>> I see. FWIW, Comparison splitdwarf+dwp and DWARFLinker from lld: >>>> >>>> 1. split-dwarf+llvm-dwp = linking time for clang 6 sec, >>>> generating time for .dwp 53 sec, clang=997M clang.dwp=1.1G. >>> FWIW, llvm-dwp is not very well optimized (which is to say: it is not >>> o...

..., only in final releases - well, >>>>>>> maybe their situation is more "neutral" - not a major pain point in >>>>>>> any case I'd guess. >>>>>>> >>>>>>> >>>>>> I see. FWIW, Comparison splitdwarf+dwp and DWARFLinker from lld: >>>>>> >>>>>> 1. split-dwarf+llvm-dwp = linking time for clang 6 sec, >>>>>> generating time for .dwp 53 sec, clang=997M clang.dwp=1.1G. >>>>> FWIW, llvm-dwp is not very well optimized (which is...

...hat similar - it's not used >> >in the iterative development cycle, only in final releases - well, >> >maybe their situation is more "neutral" - not a major pain point in >> >any case I'd guess. >> > >>> >> I see. FWIW, Comparison splitdwarf+dwp and DWARFLinker from lld: >> >> 1. split-dwarf+llvm-dwp = linking time for clang 6 sec, >> generating time for .dwp 53 sec, clang=997M clang.dwp=1.1G. >FWIW, llvm-dwp is not very well optimized (which is to say: it is not >optimized), binutils dwp might be a better...

...>>>> maybe their situation is more "neutral" - not a major pain > point in > >>>>>>> any case I'd guess. > >>>>>>> > >>>>>>> > >>>>>> I see. FWIW, Comparison splitdwarf+dwp and DWARFLinker from > lld: > >>>>>> > >>>>>> 1. split-dwarf+llvm-dwp = linking time for clang 6 sec, > >>>>>>       generating time for .dwp 53 sec, clang=997M > clang.dwp=1.1G. > >>>>&g...

...be their situation is more "neutral" - not a major pain point >>> in >>> >>>>>>> any case I'd guess. >>> >>>>>>> >>> >>>>>>> >>> >>>>>> I see. FWIW, Comparison splitdwarf+dwp and DWARFLinker from lld: >>> >>>>>> >>> >>>>>> 1. split-dwarf+llvm-dwp = linking time for clang 6 sec, >>> >>>>>> generating time for .dwp 53 sec, clang=997M clang.dwp=1.1G. >>> >>>>>...

...> >I imagine Apple's use for dsymutil is somewhat similar - it's not used >in the iterative development cycle, only in final releases - well, >maybe their situation is more "neutral" - not a major pain point in >any case I'd guess. > I see. FWIW, Comparison splitdwarf+dwp and DWARFLinker from lld: 1. split-dwarf+llvm-dwp = linking time for clang 6 sec, generating time for .dwp 53 sec, clang=997M clang.dwp=1.1G. 2. DWARFLinker from lld = linking time for clang 72 sec, clang=760M. >> Thus if they would use this LLD feature in its current state >&g...

...their situation is more "neutral" - not a major pain point in >>>> >>>>>>> any case I'd guess. >>>> >>>>>>> >>>> >>>>>>> >>>> >>>>>> I see. FWIW, Comparison splitdwarf+dwp and DWARFLinker from lld: >>>> >>>>>> >>>> >>>>>> 1. split-dwarf+llvm-dwp = linking time for clang 6 sec, >>>> >>>>>> generating time for .dwp 53 sec, clang=997M clang.dwp=1.1G. >>>> >...

> On Nov 17, 2016, at 3:40 PM, David Blaikie <dblaikie at gmail.com> wrote: > > > > On Thu, Nov 17, 2016 at 3:12 PM Greg Clayton via llvm-dev <llvm-dev at lists.llvm.org> wrote: > I have recently been modifying the DWARF parser and have more patches planned and I want to be able to add unit tests that test the internal llvm DWARF APIs to ensure they continue to

...ng only two files (executable and .dwp) looks significantly better than having executable and multiple .dwo files. > > > > Having only one file(executable) with minimal size looks better than the two files with a bigger size. > > > > > > > > clang compiled with -gsplitdwarf takes 0.9G for executable and 0.9G for .dwp. > > > > clang compiled with -gc-debuginfo takes only 0.76G for single executable. > > > > > > > > > > > > > > > > >>For the first point: we have a problem "Overlapping address ranges...