From: Alexandra Petlanova Hajkova <ahajkova@redhat.com>
To: Ed Catmur <ed@catmur.uk>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Support DW_TAG_GNU_formal_parameter_pack and DW_TAG_GNU_template_parameter_pack.
Date: Tue, 7 Feb 2023 06:55:50 +0100 [thread overview]
Message-ID: <CAJVr-EOFsm3Ya5Vaz1--Mgd+BAm5L4=CxibuxHmJePW4NQqsYw@mail.gmail.com> (raw)
In-Reply-To: <74d9a924-d892-4a50-a82c-ab9e8e42ee33@app.fastmail.com>
[-- Attachment #1: Type: text/plain, Size: 801 bytes --]
On Sat, Feb 4, 2023 at 5:33 PM Ed Catmur <ed@catmur.uk> wrote:
> On Tue, 17 Jan 2023, at 16:41, Alexandra Petlanova Hajkova wrote:
> >
> >
> > On Sun, Jan 15, 2023 at 11:43 PM Ed Catmur <ed@catmur.uk> wrote:
> >> https://sourceware.org/bugzilla/show_bug.cgi?id=17272
> >>
> >> Synthesize 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.
> >> ---
> >
> > Great patch but maybe your commit message could be slightly more
> informative.
>
> Thanks, resent with a better description:
> https://sourceware.org/pipermail/gdb-patches/2023-February/196618.html
Good to go from my point of view.
next prev parent reply other threads:[~2023-02-07 5:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-15 22:42 Ed Catmur
[not found] ` <CAJVr-ENd09JAo9qcQHTx2ifERHdJOVM=nAHWdaOOFEWLA8gORg@mail.gmail.com>
2023-01-23 10:00 ` Fwd: " Alexandra Petlanova Hajkova
2023-02-04 16:32 ` Ed Catmur
2023-02-07 5:55 ` Alexandra Petlanova Hajkova [this message]
2023-05-30 17:28 ` Tom Tromey
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-EOFsm3Ya5Vaz1--Mgd+BAm5L4=CxibuxHmJePW4NQqsYw@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).