public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "ed at catmur dot uk" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/28946] Missing template paramater pack support
Date: Tue, 17 Jan 2023 01:00:05 +0000	[thread overview]
Message-ID: <bug-28946-4717-RxLAIRwIzf@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28946-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=28946

Ed Catmur <ed at catmur dot uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ed at catmur dot uk

--- Comment #6 from Ed Catmur <ed at catmur dot uk> ---
Hi David, can you let me know whether clang would be able to make use of the
fix in #17272 (see attached patch, linked PR, linked ML post, whatever works
for you)? It would be useful to know whether someone would be able to make use
of it, even if gcc aren't interested in supporting
DW_TAG_GNU_template_parameter_pack.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      parent reply	other threads:[~2023-01-17  1:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-05 16:08 [Bug gdb/28946] New: " jengelh at inai dot de
2022-03-06 14:20 ` [Bug gdb/28946] " ssbssa at sourceware dot org
2022-03-06 14:55 ` ssbssa at sourceware dot org
2022-03-06 16:49 ` [Bug c++/28946] " tromey at sourceware dot org
2022-10-27 21:56 ` dblaikie at gmail dot com
2023-01-14 12:58 ` ssbssa at sourceware dot org
2023-01-14 19:13 ` dblaikie at gmail dot com
2023-01-16 23:37 ` tromey at sourceware dot org
2023-01-17  1:00 ` ed at catmur dot uk [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=bug-28946-4717-RxLAIRwIzf@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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).