search for: dw_at_use_utf8

> With time, you might get to a point where Dwarf is a first-class > citizen and there will be basic compatibility checks in "make check" > and a build bot for GDB test suite on some platforms, but to get > there, you'll go through a lot of pain. > Hopefully not too much. Paul has been helping and I add tests whenever I fix something, but a quality suite is something

...g emission code. > > I've tried to formally implement a few things, but in general it was > ad-hoc for so long this is true. Yeah, clearly some DWARF 3 bits are creeping in, and more will come. (I have some UTF-8 work waiting for a chance to be cleaned up and submitted, for example. DW_AT_use_UTF8 is a DWARF 3 attribute.) But if some people really are stuck in DWARF 2 land, we might have to do something intelligent about it. (I'd rather not, I'd rather have LLVM assert that DWARF 3 is where it's at. I mean really, DWARF 3 was published in 2005!) --paulr

On 30 January 2018 at 15:41, Adrian Prantl <aprantl at apple.com> wrote: > > >> On Jan 30, 2018, at 7:35 AM, Pavel Labath <labath at google.com> wrote: >> >> Hello all, >> >> I am looking for feedback regarding implementation of the case folding >> algorithm for .debug_names hashes. >> >> Unlike the apple tables, the .debug_names

On 17 October 2012 21:09, Eric Christopher <echristo at gmail.com> wrote: >> 1) What level of interest is there in Dwarf backward compatibility; > > I don't have a lot of interest in keeping dwarf backward compatibility > past my ability to test things, hence the option for darwin's gdb. Very few people have, and Dwarf is not an easy target, so the cost of having a

> On Jan 30, 2018, at 7:35 AM, Pavel Labath <labath at google.com> wrote: > > Hello all, > > I am looking for feedback regarding implementation of the case folding > algorithm for .debug_names hashes. > > Unlike the apple tables, the .debug_names hashes are computed from > case-folded names (to enable case-insensitive lookups for languages > where that makes

...emission code. > > I've tried to formally implement a few things, but in general it was > ad-hoc for so long this is true. Yeah, clearly some DWARF 3 bits are creeping in, and more will come. (I have some UTF-8 work waiting for a chance to be cleaned up and submitted, for example. DW_AT_use_UTF8 is a DWARF 3 attribute.) But if some people really are stuck in DWARF 2 land, we might have to do something intelligent about it. (I'd rather not, I'd rather have LLVM assert that DWARF 3 is where it's at. I mean really, DWARF 3 was published in 2005!) --paulr _______________________...