search for: gsplitdwarf

...tly, but yes, it looks less useful comparing to D74169. Having 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 starting from 0"(D59553). >>We use custom solution, but the general solution like D7416...

...74169. > > Having 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 > starting from 0"(D59553). > >...

...table 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 addres...

...oks less useful comparing to D74169. > Having 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 starting from 0"(D59553). > > >>We use custom solution, bu...

...aring to D74169. > > Having 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 starting from 0"(D59553). > > > >...

...aring to D74169. > > Having 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 starting from 0"(D59553). > > > >...

...; > > Having 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 starting from 0"(D59...

...ing 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...

...les (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 "Ov...

...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 "Overlap...

...ficantly > 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. > > >> > > > > > >> > > > > > >> > > > > > >> > > >...

...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: w...

Hi David, Excuse me for delayed answer. It took some time to prepare. Please, find the answers bellow... >Broad question: Do you have any specific motivation/users/etc in implementing this (if you can speak about it)? > - it might help motivate the work, understand what tradeoffs might be suitable for you/your users, etc. There are two general requirements: 1) Remove (or clean) invalid

...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 "Overlap...

...) 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...

...tter 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. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>...

...t; > 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. > > > > > > > > > > > > > > > > > > > >...

...iple .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. > >>>>>>>>>> > >>>>>>>>>> > &gt...

...>>> >>>>>>>>>> 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. >>> >>>>>>>>>> >>> >>>>>>>>&...

.... >>>> >>>>>>>>>> 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. >>>> >>>>>>>>>> >>>> >>>>>>>>>> >&g...