Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Keith Seitz <keiths@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2] infcall: Add support for integer literals as reference function paramters
Date: Tue, 21 Oct 2025 14:19:10 -0600	[thread overview]
Message-ID: <877bwom2ip.fsf@tromey.com> (raw)
In-Reply-To: <f5fff161e92f0acd0cc06b0f3bc6b774ae603927.1760988969.git.keiths@redhat.com> (Keith Seitz's message of "Mon, 20 Oct 2025 12:36:09 -0700")

>>>>> "Keith" == Keith Seitz <keiths@redhat.com> writes:

Keith> This patch attempts to mitigate the shortcomings of passing literals
Keith> to inferior function calls requiring references.  The specific use case here
Keith> is std::map's operator[]:

Thanks for doing this.

Keith>  struct value *
Keith> -value_coerce_to_target (struct value *val)
Keith> +value_coerce_to_target (struct value *val, struct type *param_type)
Keith>  {

I wasn't totally sold on doing the work here and not in value_arg_coerce
but I guess it makes sense.

Keith> +  if (param_type != nullptr && param_type->language () == language_cplus
Keith> +      && TYPE_IS_REFERENCE (param_type))
Keith> +    {

Can we get here with a value that has an address, and so we don't need
to make a copy?  Like if there's a local variable 'x', and you do 'print
map[x]'?

If the argument is already in memory, then just casting its address to a
reference would be a lot better, especially because memcpy()ing the data
into the inferior is only really correct for trivially-copyable types.

I don't know if that property (trivially-copyable) is all that easy to
detect in gdb, but if it is, I guess it would make sense to detect it
and throw an exception.  Since in that case we'd be looking at something
like a callee that wants memory but where the object has been SROA'd or
something along those lines.

Tom

  reply	other threads:[~2025-10-21 20:19 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-16 15:48 [PATCH] " Keith Seitz
2025-10-17 14:49 ` Tom Tromey
2025-10-20 19:00   ` Keith Seitz
2025-10-20 19:36 ` [PATCH v2] " Keith Seitz
2025-10-21 20:19   ` Tom Tromey [this message]
2025-10-22 12:05     ` Andrew Burgess
2025-10-22 13:21       ` Tom Tromey
2026-01-22 19:05       ` Keith Seitz
2026-01-23 14:07         ` Aktemur, Tankut Baris
2026-01-27 18:43           ` Keith Seitz
2026-01-27 19:01 ` [PATCH v4] " Keith Seitz
2026-01-28  8:24   ` Aktemur, Tankut Baris
2026-01-28 13:54   ` Andrew Burgess
2026-02-02 17:05     ` Aktemur, Tankut Baris
2026-02-02 17:21     ` Keith Seitz
2026-01-30 20:59   ` Tom Tromey
2026-02-02 16:58     ` Keith Seitz
2026-02-02 17:22       ` Aktemur, Tankut Baris
2026-02-12 16:31       ` Tom Tromey
2026-03-12 14:14 ` [PATCH v5] infcall: Add support for integer literals as reference function parameters Keith Seitz
2026-03-12 16:23   ` Tom de Vries
2026-03-12 16:45     ` Keith Seitz
2026-03-12 17:12 ` [PATCH v6] " Keith Seitz
2026-03-17 14:10   ` Andrew Burgess
2026-03-17 18:11     ` Keith Seitz

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=877bwom2ip.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=gdb-patches@sourceware.org \
    --cc=keiths@redhat.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