public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Ulrich Weigand <Ulrich.Weigand@de.ibm.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	Aditya Kamath1 <Aditya.Kamath1@ibm.com>
Cc: Sangamesh Mallayya <sangamesh.swamy@in.ibm.com>
Subject: Re: [PATCH] Fix for call feature having nine parameters or more in AIX
Date: Fri, 25 Aug 2023 15:57:46 +0000	[thread overview]
Message-ID: <c9807cd0375ebf70c831eb3295dcd110ddc0e7c3.camel@de.ibm.com> (raw)
In-Reply-To: <CH2PR15MB35441D42C7C5AC66140A1EA5D6E3A@CH2PR15MB3544.namprd15.prod.outlook.com>

Aditya Kamath1 <Aditya.Kamath1@ibm.com> wrote:

>Hope this looks good now. Kindly let me know. If not kindly push these changes.

Just a few comments remaining:

>+         space += ((len - argbytes + wordsize -1) & -wordsize);
Please use "- 1" instead of "-1" everywhere here.

>+         write_memory (sp + 24 + (ii * wordsize),
I think this needs to be 6 * wordsize instead of 24 here too.

>+         if (wordsize == 8 &&  
>+            (type->code () == TYPE_CODE_INT
>+             || type->code () == TYPE_CODE_ENUM
>+             || type->code () == TYPE_CODE_BOOL
>+             || type->code () == TYPE_CODE_CHAR ))
>+           {
I'm not sure the "wordsize == 8" check is correct here.  It's of course
a question of how the 32-bit AIX ABI is defined, but for parameters in
registers, we do the extension on 32-bit too.  So it seems likely to me
that we need to do it for parameters in memory as well.

Bye,
Ulrich


  reply	other threads:[~2023-08-25 15:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-25  9:21 Aditya Kamath1
2023-08-25 11:19 ` Ulrich Weigand
2023-08-25 13:35   ` Aditya Kamath1
2023-08-25 14:13     ` Ulrich Weigand
2023-08-25 15:35       ` Aditya Kamath1
2023-08-25 15:57         ` Ulrich Weigand [this message]
2023-08-25 16:36           ` Aditya Kamath1
2023-08-25 16:49             ` Ulrich Weigand
2023-08-25 17:47               ` Aditya Kamath1

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=c9807cd0375ebf70c831eb3295dcd110ddc0e7c3.camel@de.ibm.com \
    --to=ulrich.weigand@de.ibm.com \
    --cc=Aditya.Kamath1@ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=sangamesh.swamy@in.ibm.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).