search for: d91404

...quite contrived. A reply I just made https://lists.llvm.org/pipermail/llvm-dev/2020-November/146673.html detailed why I don't like the conceptual model: the behavior is dependent on other sections. I also felt bad as I had to do string comparison on ".debug_" (https://reviews.llvm.org/D91404) I've chatted with gdb folks: gdb (gdb/dwarf2/read.c) is agnostic about the section type. (They just cannot handle multiple .debug_info sections.) SHT_PROGBITS is a default (or "use this if nothing more specific exists") section type that probably no tool will specifically check the...

...that if a ".debug_info" section contains >only 64-bit relocations, all other debug info sections in the object >file are in the 64-bit DWARF format. This can be simplified to >checking just the first relocation of this section, as you have made >in https://reviews.llvm.org/D91404, and then spreading the assessment >to all other debug sections in the object file. Sure, this heuristic >will not work for some clumsy partially linked relocatable objects >with a mixture of DWARF64 and DWARF32 data, but I guess they can be >ignored for the first shot, because, fir...

...we can conclude that if a ".debug_info" section contains only 64-bit relocations, all other debug info sections in the object file are in the 64-bit DWARF format. This can be simplified to checking just the first relocation of this section, as you have made in https://reviews.llvm.org/D91404, and then spreading the assessment to all other debug sections in the object file. Sure, this heuristic will not work for some clumsy partially linked relocatable objects with a mixture of DWARF64 and DWARF32 data, but I guess they can be ignored for the first shot, because, firstly, their crea...

...ude that if a ".debug_info" section contains >only 64-bit relocations, all other debug info sections in the object >file are in the 64-bit DWARF format. This can be simplified to >checking just the first relocation of this section, as you have made >in https://reviews.llvm.org/D91404 , and then spreading the assessment >to all other debug sections in the object file. Sure, this heuristic >will not work for some clumsy partially linked relocatable objects >with a mixture of DWARF64 and DWARF32 data, but I guess they can be >ignored for the first shot, because, firstl...

...https://lists.llvm.org/pipermail/llvm-dev/2020-November/146673.html >> detailed why I don't like the conceptual model: the behavior is >> dependent on other sections. >> I also felt bad as I had to do string comparison on ".debug_" >> (https://reviews.llvm.org/D91404) >> >> I've chatted with gdb folks: gdb (gdb/dwarf2/read.c) is agnostic about >> the section type. (They just cannot handle multiple .debug_info >> sections.) >> SHT_PROGBITS is a default (or "use this if nothing more specific >> exists") section ty...

...I just made > https://lists.llvm.org/pipermail/llvm-dev/2020-November/146673.html > detailed why I don't like the conceptual model: the behavior is > dependent on other sections. > I also felt bad as I had to do string comparison on ".debug_" > (https://reviews.llvm.org/D91404) > > I've chatted with gdb folks: gdb (gdb/dwarf2/read.c) is agnostic about > the section type. (They just cannot handle multiple .debug_info > sections.) > SHT_PROGBITS is a default (or "use this if nothing more specific > exists") section type that probably no tool...

...org/pipermail/llvm-dev/2020-November/146673.html > >> detailed why I don't like the conceptual model: the behavior is > >> dependent on other sections. > >> I also felt bad as I had to do string comparison on ".debug_" > >> (https://reviews.llvm.org/D91404) > >> > >> I've chatted with gdb folks: gdb (gdb/dwarf2/read.c) is agnostic about > >> the section type. (They just cannot handle multiple .debug_info > >> sections.) > >> SHT_PROGBITS is a default (or "use this if nothing more specific > &gt...

Looks like there is an agreement that this path, modifying lld to order sections using relocations, should be explored. If Igor doesn't object, since he was primary one driving DWARF64 so far, I would like to give it a shot at implementing and collecting some performance numbers. 🙂 Alex ________________________________ From: James Henderson <jh7370.2008 at my.bristol.ac.uk> Sent:

On Fri, Nov 13, 2020 at 11:29 AM David Blaikie <dblaikie at gmail.com> wrote: > > On Fri, Nov 13, 2020 at 11:24 AM Fāng-ruì Sòng <maskray at google.com> wrote: > > > > On Fri, Nov 13, 2020 at 11:17 AM David Blaikie <dblaikie at gmail.com> wrote: > > > > > > On Fri, Nov 13, 2020 at 11:05 AM Fāng-ruì Sòng <maskray at google.com> wrote: >