Displaying 3 results from an estimated 3 matches for "pr43622".
2019 Oct 09
3
DebugInfo work contribution and update.
...on 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 - bu...
2019 Oct 09
4
DebugInfo work contribution and update.
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
2019 Oct 09
5
DebugInfo work contribution and update.
...ts and cfe-commits lists to notice when people
> are posting patches; post your own patches; and ask on the dev lists. If
> you decide to work on something that was reported as a bug, post a note
> there or assign the bug to yourself.
>
>
>
> I looked up the two PRs you cited; PR43622 is likely a simple oversight
> that should be easy to fix. PR43263 doesn’t appear to be related to debug
> info, was that a typo?
>
> --paulr
>
>
>
> *From:* Sourabh Singh Tomar <sourav0311 at gmail.com>
> *Sent:* Wednesday, October 09, 2019 2:38 PM
> *To:* Davi...