From: "Bouhaouel, Mohamed" <mohamed.bouhaouel@intel.com>
To: Simon Marchi <simark@simark.ca>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: [PATCH 0/2] Add more flexibility to inferior call
Date: Fri, 24 Mar 2023 14:10:31 +0000 [thread overview]
Message-ID: <DM6PR11MB4457A99450295A1944817732E4849@DM6PR11MB4457.namprd11.prod.outlook.com> (raw)
In-Reply-To: <8a75f1cd-a09a-2e34-f294-89d253d4d46a@simark.ca>
That makes sense, I will re-submit them once the new architecture is posted.
Thanks.
Mohamed
> -----Original Message-----
> From: Simon Marchi <simark@simark.ca>
> Sent: Friday, March 24, 2023 2:38 PM
> To: Bouhaouel, Mohamed <mohamed.bouhaouel@intel.com>; gdb-
> patches@sourceware.org
> Subject: Re: [PATCH 0/2] Add more flexibility to inferior call
>
> On 3/23/23 07:34, Bouhaouel, Mohamed wrote:
> > Hi Simon,
> >
> > Thanks for your feedback. These patches are pre-requisite for an Intel
> architecture
> > that has not been yet up-streamed. Waiting for the architecture to be
> introduced
> > first is likely more logical, although, such flexibility might be useful for
> > other new architectures.
> >
> > Should I submit a new version of those patches while considering your
> comments
> > or wait to post all together?
>
> I think it's better to post it with the first architecture that uses it.
> It helps illustrate what the method is for and how it works. But also,
> if your port never ends up upstream for whatever reason, it doesn't make
> sense to have those methods with no users.
>
> Simon
Intel Deutschland GmbH
Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de <http://www.intel.de>
Managing Directors: Christin Eisenschmid, Sharon Heck, Tiffany Doon Silva
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
next prev parent reply other threads:[~2023-03-24 14:10 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 [this message]
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=DM6PR11MB4457A99450295A1944817732E4849@DM6PR11MB4457.namprd11.prod.outlook.com \
--to=mohamed.bouhaouel@intel.com \
--cc=gdb-patches@sourceware.org \
--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).