public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Alexandra Petlanova Hajkova <ahajkova@redhat.com>
To: Ed Catmur <ed@catmur.uk>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2][PR 17272] Support DWARF tags for C++11 variadic templates
Date: Tue, 7 Feb 2023 06:57:10 +0100	[thread overview]
Message-ID: <CAJVr-EO1LWLu+HY320V47ADP=PmOH3-xRes3eCPEqK2DdViOfQ@mail.gmail.com> (raw)
In-Reply-To: <20230204162755.2831-1-ed@catmur.uk>

[-- Attachment #1: Type: text/plain, Size: 1191 bytes --]

On Sat, Feb 4, 2023 at 5:28 PM Ed Catmur <ed@catmur.uk> wrote:

> This patch adds support for DW_TAG_GNU_formal_parameter_pack and
> DW_TAG_GNU_template_parameter_pack, added to DWARF in March 2009 for
> C++11 variadic templates[1].
>
> They are not currently emitted thanks to a typo[2] but the fix is
> trivial[3] and has been repeatedly submitted[4] to gcc; I'm not sure
> what else I can do to get it accepted; regardless, anyone building their
> own compiler can still make use of this.
>
> This implementation synthesizes type and parameter names as T#n, p#n
> e.g. Args#1, args#1. This is a pretty simple approach but it seems to
> work OK and is compatible with the old style type and parameter names
> emitted by old versions of gcc and when it's writing stabs+ format,
> meaning that any debugger scripts will continue to work.
>
> 1. http://wiki.dwarfstd.org/index.php?title=C%2B%2B0x:_Variadic_templates
> 2. https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70536
> 3. https://github.com/ecatmur/gcc/pull/5
> 4. https://gcc.gnu.org/pipermail/gcc-patches/2023-January/609659.html
> PR. https://sourceware.org/bugzilla/show_bug.cgi?id=17272
> ---
>  I think this should be accepted.
>

      reply	other threads:[~2023-02-07  5:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-04 16:27 Ed Catmur
2023-02-07  5:57 ` Alexandra Petlanova Hajkova [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAJVr-EO1LWLu+HY320V47ADP=PmOH3-xRes3eCPEqK2DdViOfQ@mail.gmail.com' \
    --to=ahajkova@redhat.com \
    --cc=ed@catmur.uk \
    --cc=gdb-patches@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).