[llvm-dev] DebugInfo work contribution and update.

[David Blaikie via llvm-dev]

+some other debugger people (Pavel - wasn't sure which email address you
prefer, feel free to let me know (privately or publicly) for future
reference)

I work at Google & we're certainly interested in DWARFv5 compliance - I'm
currently working on improving debug_loclist emission to share more address
pool entries ( https://reviews.llvm.org/D68620 ) which includes some
improvements to llvm-dwarfdump to go with that. (Pavel's working on further
improvements https://reviews.llvm.org/D68271 )

I haven't looked at/started on the loclist issue (PR43622) - so if you want
to look at that, that's fine by me.

Are you also interested in the debugger side of things? GDB's DWARFv5
support is pretty incomplete & Ali's already looking at some of that, and I
might get to the debug_loclist improvements necessary - but if someone else
wants to do that before me, I won't complain.

Not sure of any other major holes in LLVM's DWARFv5 support, but they might
be out there, for sure.

On Wed, Oct 9, 2019 at 9:37 AM Sourabh Singh Tomar via llvm-dev <
llvm-dev at lists.llvm.org> wrote:

> Hi llvm-dev, cfe-dev,
>
> It's been a while since our team is investigating DebugInfo in LLVM, we're
> looking forward to contribute and enhance in LLVM DebugInfo.
>
> We,'ve been investigating mostly on DWARF-5 aspects -- couple of them to
> mention--
> 1. Language aspects
> 2. Location mostly optimized out ones
> 3. DebugInfo conformance to DWARF-5
>
> To avoid getting conflicted with some body else's work and avoiding
> redundancy. We would like to know the over-all state of current community
> developments happening WRT DWARF-5.
>
> As of now, we're working on --
> PR 43263, 43622 -- reported today {Just Now}
>
> we'll be up-streaming patches for these.
>
> Please let us know your thoughts, and anything else that's relevant that
> we need to aware of before picking up.
>
> Thanks in anticipation!
> Sourabh Singh Tomar
>
>
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20191009/ea32047f/attachment.html>