public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@palves.net>
To: gdb-patches@sourceware.org
Cc: Tom de Vries <tdevries@suse.de>, Tom Tromey <tom@tromey.com>
Subject: [PATCH 0/1] Introduce gdb::make_function_view
Date: Fri, 22 Jul 2022 12:02:02 +0100	[thread overview]
Message-ID: <20220722110203.4152339-1-pedro@palves.net> (raw)

This adds gdb::make_function_view, which let's you create a function
view from a callable without specifying the function_view's template
parameter type.  The need for this came up in this thread:

  https://sourceware.org/pipermail/gdb-patches/2022-July/190985.html

Pedro Alves (1):
  Introduce gdb::make_function_view

 gdb/unittests/function-view-selftests.c |  82 ++++++++++++++-
 gdbsupport/function-view.h              | 127 ++++++++++++++++++++++++
 2 files changed, 208 insertions(+), 1 deletion(-)


base-commit: 6577f365ebdee7dda71cb996efa29d3714cbccd0
-- 
2.36.0


             reply	other threads:[~2022-07-22 11:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-22 11:02 Pedro Alves [this message]
2022-07-22 11:02 ` [PATCH 1/1] " Pedro Alves

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=20220722110203.4152339-1-pedro@palves.net \
    --to=pedro@palves.net \
    --cc=gdb-patches@sourceware.org \
    --cc=tdevries@suse.de \
    --cc=tom@tromey.com \
    /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).