public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
Cc: "Bouhaouel, Mohamed" <mohamed.bouhaouel@intel.com>,
	 Simon Marchi <simark@simark.ca>
Subject: Re: [PATCH 0/2] Add more flexibility to inferior call
Date: Fri, 24 Mar 2023 08:12:42 -0600	[thread overview]
Message-ID: <877cv6fdb9.fsf@tromey.com> (raw)
In-Reply-To: <8a75f1cd-a09a-2e34-f294-89d253d4d46a@simark.ca> (Simon Marchi via Gdb-patches's message of "Fri, 24 Mar 2023 09:38:14 -0400")

Simon> I think it's better to post it with the first architecture that uses it.

Agreed.

Simon> It helps illustrate what the method is for and how it works.  But also,
Simon> if your port never ends up upstream for whatever reason, it doesn't make
Simon> sense to have those methods with no users.

Additionally, depending on exactly what it is needed for, there might be
some other solution, not involving new arch hooks, that we'd prefer.

Tom

      parent reply	other threads:[~2023-03-24 14:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-22 17:13 Mohamed Bouhaouel
2023-03-22 17:13 ` [PATCH 1/2] gdb, gdbarch, infcall: Add value_arg_coerce method to gdbarch Mohamed Bouhaouel
2023-03-22 19:18   ` Simon Marchi
2023-03-22 17:13 ` [PATCH 2/2] gdb, gdbarch, infcall: Add reserve_stack_space " Mohamed Bouhaouel
2023-03-22 19:16 ` [PATCH 0/2] Add more flexibility to inferior call Simon Marchi
2023-03-23 11:34   ` Bouhaouel, Mohamed
2023-03-24 13:38     ` Simon Marchi
2023-03-24 14:10       ` Bouhaouel, Mohamed
2023-03-24 14:12       ` Tom Tromey [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=877cv6fdb9.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=gdb-patches@sourceware.org \
    --cc=mohamed.bouhaouel@intel.com \
    --cc=simark@simark.ca \
    /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).