[PATCH] D35994: Debug info for variables whose type is shrinked to bool

David Blaikie via llvm-commits llvm-commits at lists.llvm.org
Mon Aug 28 21:04:44 PDT 2017


yeah, I'm not terribly fussed either way - we support old DWARF versions on
an as-needed basis, so someone can complain if they get DWARF parsing
errors or if they get optimized out debug info. Though while I like the
certainty of implementing on-spec, it's easier for a user to identify a
problem if they get a parsing error, I guess... :/ Seems like a dodgy way
to drive adoption of newer standards, though.

Meh.

- Dave

On Mon, Aug 28, 2017 at 10:01 AM Adrian Prantl via Phabricator <
reviews at reviews.llvm.org> wrote:

> aprantl added a comment.
>
> In fully-compliant mode we should just not emit any DWARF expression that
> ends with a DW_OP_stack_value in DWARF < 4. However, LLDB and GDB (at least
> the version Apple used to ship in Xcode) support a couple of expressions
> that are outside of the specification but do work in practice, so I'm
> reluctant to drop support for that by being stricter.
> That said, Darwin has been using DWARF 4 for a while now, so an argument
> could be made that it is okay to regress on older deployment targets for
> the sake of correctness/standards compliance.
>
>
> https://reviews.llvm.org/D35994
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20170829/1cb4d2e0/attachment.html>


More information about the llvm-commits mailing list