Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Sergio Durigan Junior <sergiodj@redhat.com>
To: "Tiago Stürmer Daitx" <tdaitx@linux.vnet.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix complex argument handling in ppc64 dummy function call
Date: Fri, 01 Mar 2013 18:57:00 -0000	[thread overview]
Message-ID: <m3sj4feyo1.fsf@redhat.com> (raw)
In-Reply-To: <20130301170811.EFEA2300943@igoo.rch.stglabs.ibm.com> ("Tiago	=?utf-8?Q?St=C3=BCrmer?= Daitx"'s message of "Fri, 1 Mar 2013 11:08:11 -0600 (CST)")

On Friday, March 01 2013, Tiago Stürmer Daitx wrote:

> Sergio, many thanks for the thorough review and the tips. There's no better 
> way to get these rules to stick in my head. ^_^

Thanks a lot!

> Let me know if there is still something amiss.

Just one little thing :-).

> +          else if (TYPE_CODE (type) == TYPE_CODE_COMPLEX
> +              && (TYPE_LENGTH (type) == 8 || TYPE_LENGTH (type) == 16))
> +            {
> +              int i;
> +
> +              for (i = 0; i < 2; i++)
> +                {
> +		  if (write_pass)
> +		    {
> +		      struct type *target_type;
> +
> +		      target_type = check_typedef (TYPE_TARGET_TYPE (type));
> +		      ppc64_sysv_abi_push_float (gdbarch, regcache, tdep,
> +						 target_type, val + i *
> +						 TYPE_LENGTH (target_type),
> +						 freg, greg, gparam);
> +		    }
> +                  freg++;
> +                  greg++;
> +                  /* Always consume parameter stack space.  */
> +                  gparam = align_up(gparam + 8, tdep->wordsize);

Space between the function name and its arguments.  It should read:

      align_up (gparam....);

But don't bother sending the patch again just for that little nit.  When
the patch gets reviewed/accepted, just commit it with the proper fix
:-).

Thanks again,

-- 
Sergio


  reply	other threads:[~2013-03-01 18:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-28 18:30 Tiago Stürmer Daitx
2013-03-01  2:55 ` Sergio Durigan Junior
2013-03-01 17:50   ` Tiago Stürmer Daitx
2013-03-01 18:57     ` Sergio Durigan Junior [this message]
2013-03-01 20:07       ` Tiago Stürmer Daitx
2013-03-01 21:24     ` Pedro Alves
2013-03-01 23:42       ` Tiago Stürmer Daitx
2013-03-11 16:12     ` Ulrich Weigand
2013-04-01  4:15       ` Tiago Stürmer Daitx
2013-04-02 13:41         ` Ulrich Weigand

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=m3sj4feyo1.fsf@redhat.com \
    --to=sergiodj@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tdaitx@linux.vnet.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