[llvm-dev] addition of vendor dwarf operator extension.

[David Blaikie via llvm-dev]

Does this have a significant impact on total DWARF size or performance that
you've observed/have data about?

On Tue, Dec 3, 2019 at 12:06 AM Chirag Patel <Chirag at raincode.com> wrote:

> Hello,
>
>
>
> Thanks for prompt reply.
>
>
>
> Motivation,
>
> In case of debugging of bi-endian dwarf and value known at runtime some of
> the raw values needs to be byte swapped to change the endianity. We have a
> llvm based compiler which generates such dwarf, TAG_variable marked as big
> endian and debugging on little endian host using lldb. The listed operator
> on dwarf issues does that, one operator instead of list of operators.
>
>
>
> Proposal,
>
> Addition of listed dwarf operator as vender extension in llvm/lldb till it
> gets released.
>
>
>
> Regards,
>
>
>
> *Chirag Patel*
>
> Software Engineer | Raincode Labs India
>
> *Tel*: (+91) 080 41159811
>
> *Mob*: (+91) 9049336744
>
> *www.raincodelabs.com <http://www.raincodelabs.com/>*
>
> [image: linkedin-button] <https://in.linkedin.com/in/chirag-patel->
>
>
>
> *From:* David Blaikie <dblaikie at gmail.com>
> *Sent:* 02 December 2019 19:51
> *To:* Chirag Patel <Chirag at raincode.com>; Adrian Prantl <aprantl at apple.com>;
> Paul Robinson <paul.robinson at sony.com>; Jonas Devlieghere <
> jdevlieghere at apple.com>
> *Cc:* llvm-dev at lists.llvm.org
> *Subject:* Re: [llvm-dev] addition of vendor dwarf operator extension.
>
>
>
> There are some vendor extensions already in LLVM/LLDB, though I guess the
> main question would be: what's the motivation?
>
>
>
> On Mon, Dec 2, 2019 at 3:14 AM Chirag Patel via llvm-dev <
> llvm-dev at lists.llvm.org> wrote:
>
> Hello all,
>
>
>
> There is one enhancement request open for dwarfv5,
> http://dwarfstd.org/ShowIssue.php?issue=191107.1
>
> The request is for addition of dwarf expression operator to swap the top
> of the dwarf stack, the response seems positive but it may take some time
> till v6.
>
> I like to add that operator as vendor extension but I am not sure how to
> go about it for llvm/lldb. Currently I am using it as vendor specific
> extension on our local fork.
>
>
>
> Does adding it as vender specific extension seems like a good idea? If yes
> please provide me the details about adding specific vendor.
>
>
>
> Regards,
>
>
>
> *Chirag Patel*
>
> Software Engineer | Raincode Labs India
>
> *Tel*: (+91) 080 41159811
>
> *Mob*: (+91) 9049336744
>
> *www.raincodelabs.com <http://www.raincodelabs.com/>*
>
> [image: linkedin-button] <https://in.linkedin.com/in/chirag-patel->
>
>
>
> _______________________________________________
> 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/20191203/86322113/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 7408 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20191203/86322113/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 7436 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20191203/86322113/attachment-0001.png>