[PATCH] D56587: Introduce DW_OP_LLVM_convert

[Alexey Bataev via Phabricator via llvm-commits]

ABataev added a comment.

In D56587#1407634 <https://reviews.llvm.org/D56587#1407634>, @dblaikie wrote:

> In D56587#1393750 <https://reviews.llvm.org/D56587#1393750>, @dblaikie wrote:
>
> > In D56587#1393746 <https://reviews.llvm.org/D56587#1393746>, @probinson wrote:
> >
> > > In D56587#1393556 <https://reviews.llvm.org/D56587#1393556>, @dblaikie wrote:
> > >
> > > > I don't think anyone mentioned it, that's why I was bringing it up - there's always an option to not render any location if it's not possible/worth the work. That's all I was asking - is it worth the complexity? (I wasn't sure anyone needed it - but sounds like Sony does, reckon it's worth the tradeoff in complexity in LLVM compared to the work required to support this in the Sony debugger?)
> > >
> > >
> > > NVPTX also would need it, because they are stuck on DWARF v2.
> >
> >
> > Any ideas if NVPTX hit this case? my understanding was that NVPTX has a fairly restrictive set of code or actions that can be used.
>
>
> Ping on this - still wondering if anyone needs the complicated code or if we could get away with the GNU extension + DWARFv5 standard


not sure, if NVPTX can hit this. It has no stack at all, so, maybe, this op won't be generated at all


CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D56587/new/

https://reviews.llvm.org/D56587