[llvm-dev] recognise DW_AT_SUN_amd64_parmdump dwarf attribute

[David Blaikie via llvm-dev]

This'll need a test case, in any case.

Adrian/Paul: Pondering this, any thoughts on how conflicts in the vendor
extension range of attributes, forms, etc, should be resolved if they ever
come up? (each vendor is free to define them as they wish, so it could be
that multiple vendors have different definitions of the same code/number &
would be ambiguous) I don't see any reason to block this patch if it
doesn't have such a conflict, since there are already other vendor
extension codes supported here for a variety of vendors - but does make me
wonder.

On Thu, Apr 27, 2017 at 2:50 AM David Gwynne via llvm-dev <
llvm-dev at lists.llvm.org> wrote:

> sun created this tag for identifying functions that dumped their
> register arguments onto the stack.
>
> this is enough for llvm-dwarfdump to recognise and print the attribute.
>
> hopefully someone will commit it.
>
> cheers,
> dlg
>
> Index: include/llvm/Support/Dwarf.def
> ===================================================================
> --- include/llvm/Support/Dwarf.def      (revision 301500)
> +++ include/llvm/Support/Dwarf.def      (working copy)
> @@ -343,6 +343,8 @@
>  HANDLE_DW_AT(0x2134, GNU_pubnames, 0, GNU)
>  HANDLE_DW_AT(0x2135, GNU_pubtypes, 0, GNU)
>  HANDLE_DW_AT(0x2136, GNU_discriminator, 0, GNU)
> +// Sun Extension
> +HANDLE_DW_AT(0x2224, SUN_amd64_parmdump, 0, GNU)
>  // Borland extensions.
>  HANDLE_DW_AT(0x3b11, BORLAND_property_read, 0, BORLAND)
>  HANDLE_DW_AT(0x3b12, BORLAND_property_write, 0, BORLAND)
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://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/20170427/4deeb11b/attachment.html>