search for: 114125

...inutils/2020-November/114116.html > > (and its reply). > > I have mentioned (a) the difficulty of the > > detecting-DWARF64-by-first-relocation approach and (b) the section > > type approach in my reply there > > https://sourceware.org/pipermail/binutils/2020-November/114125.html > > > > (a) My prototype has made me feel uneasy with this approach. > > > > <quote> > > In DWARF v4 or if .debug_str_offset is not used, it is a problem. A > > heuristic is: if an input section in a file is marked DWARF64, we mark > > all other...

...116.html > > > (and its reply). > > > I have mentioned (a) the difficulty of the > > > detecting-DWARF64-by-first-relocation approach and (b) the section > > > type approach in my reply there > > > https://sourceware.org/pipermail/binutils/2020-November/114125.html > > > > > > (a) My prototype has made me feel uneasy with this approach. > > > > > > <quote> > > > In DWARF v4 or if .debug_str_offset is not used, it is a problem. A > > > heuristic is: if an input section in a file is marked DWARF64...

...d Michael Matz: https://sourceware.org/pipermail/binutils/2020-November/114116.html (and its reply). I have mentioned (a) the difficulty of the detecting-DWARF64-by-first-relocation approach and (b) the section type approach in my reply there https://sourceware.org/pipermail/binutils/2020-November/114125.html (a) My prototype has made me feel uneasy with this approach. <quote> In DWARF v4 or if .debug_str_offset is not used, it is a problem. A heuristic is: if an input section in a file is marked DWARF64, we mark all other .debug_* DWARF64. This makes me feel a bit uneasy because for an out...

...gt; (and its reply). > > > > I have mentioned (a) the difficulty of the > > > > detecting-DWARF64-by-first-relocation approach and (b) the section > > > > type approach in my reply there > > > > https://sourceware.org/pipermail/binutils/2020-November/114125.html > > > > > > > > (a) My prototype has made me feel uneasy with this approach. > > > > > > > > <quote> > > > > In DWARF v4 or if .debug_str_offset is not used, it is a problem. A > > > > heuristic is: if an input secti...

...gt; (and its reply). > > > > I have mentioned (a) the difficulty of the > > > > detecting-DWARF64-by-first-relocation approach and (b) the section > > > > type approach in my reply there > > > > https://sourceware.org/pipermail/binutils/2020-November/114125.html > > > > > > > > (a) My prototype has made me feel uneasy with this approach. > > > > > > > > <quote> > > > > In DWARF v4 or if .debug_str_offset is not used, it is a problem. A > > > > heuristic is: if an input secti...

...ourceware.org/pipermail/binutils/2020-November/114116.html > (and its reply). > I have mentioned (a) the difficulty of the > detecting-DWARF64-by-first-relocation approach and (b) the section > type approach in my reply there > https://sourceware.org/pipermail/binutils/2020-November/114125.html > > (a) My prototype has made me feel uneasy with this approach. > > <quote> > In DWARF v4 or if .debug_str_offset is not used, it is a problem. A > heuristic is: if an input section in a file is marked DWARF64, we mark > all other .debug_* DWARF64. This makes me fee...

> Thinking about it, I wouldn't expect an LTO generated object itself to have a mixture of DWARF32/64, although I guess the 32/64 bit state could be encoded in the IR (I am not familiar enough with it to know if it actually is or not). It might be necessary to find ways to configure LTO to generate DWARF64, possibly via a link-time option. I don’t think we need to encode dwarf32/64 in IR