From: Simon Marchi <simark@simark.ca>
To: Mohamed Bouhaouel <mohamed.bouhaouel@intel.com>,
gdb-patches@sourceware.org
Subject: Re: [PATCH 0/2] Add more flexibility to inferior call
Date: Wed, 22 Mar 2023 15:16:30 -0400 [thread overview]
Message-ID: <88985e8e-be62-e407-3cca-8b554e3f4665@simark.ca> (raw)
In-Reply-To: <20230322171352.9087-1-mohamed.bouhaouel@intel.com>
On 3/22/23 13:13, Mohamed Bouhaouel via Gdb-patches wrote:
> Hi all,
>
> The following two patches would add more flexibility to the infcalls
> workflow by allowing targets to have their own implementations of:
> * value_arg_coerce: Enable the target to control arguments
> coercion whenever needed (e.g. Coerce BOOL to UINT16_T
> instead of UINT32_T).
> * reserve_stack_space: Enable the target to decide how much
> space is needed for a type (e.g. Targets might have a vectorized
> representation of variables).
Hi Mohamed,
Is there an end goal to this? It doesn't really make sense to add
gdbarch methods but have no architecture use it. If it's necessary for
some upcoming feature, then include these patches as preparatory patches
in the series that adds said feature.
Simon
next prev parent reply other threads:[~2023-03-22 19:16 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 ` Simon Marchi [this message]
2023-03-23 11:34 ` [PATCH 0/2] Add more flexibility to inferior call Bouhaouel, Mohamed
2023-03-24 13:38 ` Simon Marchi
2023-03-24 14:10 ` Bouhaouel, Mohamed
2023-03-24 14:12 ` 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=88985e8e-be62-e407-3cca-8b554e3f4665@simark.ca \
--to=simark@simark.ca \
--cc=gdb-patches@sourceware.org \
--cc=mohamed.bouhaouel@intel.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).