[llvm-dev] DebugInfo work contribution and update.

David Blaikie via llvm-dev llvm-dev at lists.llvm.org
Thu Oct 10 11:40:15 PDT 2019

On Wed, Oct 9, 2019 at 1:33 PM Robinson, Paul <paul.robinson at sony.com>

> > From: David Blaikie <dblaikie at gmail.com>
> >> On Wed, Oct 9, 2019 at 11:59 AM Robinson, Paul <mailto:
> paul.robinson at sony.com> wrote:
> >> There are many bits of DWARF-5 that haven’t been implemented.
> >
> > Got a short list, by chance?
> I can't say I've been keeping track of all that has gone in, but based
> on the list that I came up with when I was sizing the initial DWARF 5
> work, things that might not be done include:
> Default location entry
> Inline namespace attribute
> Reference-qualified member functions
> "auto" return type
> Type/item alignment
> Defaulted template parameter
> Atomic type modifier
> DW_OP_implicit_pointer
> .debug_macro section
> Typed expressions
> Supplementary objects

Ah, thanks for the list - mostly I'm interested in cases where Clang's
output is not valid DWARFv5 when requested - the new features DWARFv5
enables/allows but doesn't require are lower priority to me. Which I don't
think too much is left - DWARFv5 loclists in split DWARF is one I know of &
might get to if someone else doesn't do it before me - I'm currently
improving loclist emission (quality of implementation - using fewer address
pool entries & just general code cleanup to share some of teh
implementation with rnglist emission, not a compliance issue)

> Things I have noticed going in recently:
> Call-site and entry-value stuff (is that complete?)
> New language/dialect codes
> Deleted/defaulted members is in progress
> "noreturn" functions is in progress
> I can't remember whether split-DWARF is fully v5 compliant...
> If any items above are in fact done, my apologies and VERY happy to be
> corrected.
> --paulr
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20191010/35519f98/attachment.html>

More information about the llvm-dev mailing list