search for: dwarfutil

...39;m not aware of? (I haven't > actually used dwz, so I might have some mistaken ideas about how it > should work) > > If it's going to solve the same general problem, but be in the llvm > project instead, then maybe it should be called llvm-dwz. It looks like dwz and llvm-dwarfutil are not exactly matched in functionality. dwz is a  program that attempts to optimize DWARF debugging information contained in ELF shared libraries and ELF executables for *size*. llvm-dwarfutil is a tool that is used for processing debug info(DWARF) located in built binary files to improve debu...

...39;t actually used dwz, so I might have some mistaken >> ideas about how it should work) >> >> If it's going to solve the same general problem, but be in the >> llvm project instead, then maybe it should be called llvm-dwz. > It looks like dwz and llvm-dwarfutil are not exactly matched in > functionality. > > dwz is a  program that attempts to optimize DWARF debugging > information > contained in ELF shared libraries and ELF executables for *size*. > > llvm-dwarfutil is a tool that is used for processing debug >...

Hi,   We propose llvm-dwarfutil - a dsymutil-like tool for ELF.   Any thoughts on this?   Thanks in advance, Alexey. ====================================================================== llvm-dwarfutil(Apndx A) - is a tool that is used for processing debug info(DWARF) located in built binary files to improve debug info qual...

Debuginfo folks, What is your opinion on this proposal? Do we need to work on better DWARFLinker library for now? or Can we start to integrate llvm-dwarfutil as a series of small patches? If it is OK to start integrating of llvm-dwarfutil, Is it OK to move llvm-objcopy implementation into separate library ObjCopy ? Thank you, Alexey. On 01.09.2020 20:18, James Y Knight wrote: > > > On Mon, Aug 31, 2020 at 11:06 AM Alexey <avl.lapshin at...

...ave some mistaken ideas about how it should work) >>> >>> If it's going to solve the same general problem, but be in >>> the llvm project instead, then maybe it should be called >>> llvm-dwz. >> It looks like dwz and llvm-dwarfutil are not exactly matched >> in functionality. >> >> dwz is a  program that attempts to optimize DWARF debugging >> information >> contained in ELF shared libraries and ELF executables for *size*. >> >> llvm-dwarfutil i...

...compiled from several object files). For linked binary that means all DIEs are loaded into the memory. In the result it requires a lot of memory resources. The solution for this problem could be changing splitting of source data from the file to the compilation unit basis. yes, making dsymutil/dwarfutil to work on compilation unit basis supporting multi-threading is a quite a big piece of work. It looks like it would be good for both dsymutil and dwarfutil. > 4) Given that DWARF v6 doesn't exist yet, I wouldn't include that as > an option name just yet...! Would "maxpc&quot...

...) without significant performance degradation. 3. DWARFLinker does not support split dwarf at the moment. All these reasons are not blockers. And I believe implementation from D74169 might be integrated and incrementally improved if there would be agreement on that. Using DWARFLinker from llvm-dwarfutil is another possibility to use and improve it. When finally implemented - llvm-dwarfutil should solve the above three issues and there would probably be more reasons to include DWARFLinker into lld. Even if we would have the best solution - it is still useful to have a tool like llvm-dwarfutil f...

...should work) >>>> >>>> If it's going to solve the same general problem, but be >>>> in the llvm project instead, then maybe it should be >>>> called llvm-dwz. >>> It looks like dwz and llvm-dwarfutil are not exactly >>> matched in functionality. >>> >>> dwz is a  program that attempts to optimize DWARF >>> debugging information >>> contained in ELF shared libraries and ELF executables >>>...

...latform and supports another set of > command-line options. > > 2. add new functionality into llvm-objcopy. llvm-objcopy already supports > various binary objects formats(MachO,ELF,COFF,wasm). It also has several > options to work with debug-info. > > 3. create new utility llvm-dwarfutil which would implement the above > functionality and reuse DWARFLinker(extracted from dsymutil) library and > new library ObjectCopy(extracted from llvm-objcopy). > > So far our preference is number three. The reason for this is that separate > utility specifically working with debug...

...> > command-line options. > > > > 2. add new functionality into llvm-objcopy. llvm-objcopy already supports > > various binary objects formats(MachO,ELF,COFF,wasm). It also has several > > options to work with debug-info. > > > > 3. create new utility llvm-dwarfutil which would implement the above > > functionality and reuse DWARFLinker(extracted from dsymutil) library and > > new library ObjectCopy(extracted from llvm-objcopy). > > > > So far our preference is number three. The reason for this is that separate > > utility specifi...

...on a non-darwin platform and supports another set of command-line options. 2. add new functionality into llvm-objcopy. llvm-objcopy already supports various      binary objects formats(MachO,ELF,COFF,wasm). It also has several options      to work with debug-info. 3. create new utility llvm-dwarfutil which would implement the above functionality      and reuse DWARFLinker(extracted from dsymutil) library and new library      ObjectCopy(extracted from llvm-objcopy). So far our preference is number three. The reason for this is that separate utility specifically working with debug info looks...

On 28.07.2020 19:28, David Blaikie wrote: > On Tue, Jul 28, 2020 at 8:55 AM Alexey Lapshin <avl.lapshin at gmail.com> wrote: >> >> On 28.07.2020 10:29, David Blaikie via llvm-dev wrote: >>> On Fri, Jun 26, 2020 at 9:28 AM Alexey Lapshin >>> <alapshin at accesssoftek.com> wrote: >>>>>>>>>>>> This idea goes in another