Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: "Tiago Stürmer Daitx" <tdaitx@linux.vnet.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix printing functions with complex return on PPC64
Date: Mon, 26 Nov 2012 09:44:00 -0000	[thread overview]
Message-ID: <20121126094346.GA12249@host2.jankratochvil.net> (raw)
In-Reply-To: <50a7b46b.6jsIRrSz9fiMZdfw%tdaitx@linux.vnet.ibm.com>

On Sat, 17 Nov 2012 16:59:39 +0100, Tiago Stürmer Daitx wrote:
> --- a/gdb/ppc-sysv-tdep.c
> +++ b/gdb/ppc-sysv-tdep.c
> @@ -1925,7 +1925,8 @@ ppc64_sysv_abi_return_value (struct gdbarch *gdbarch, struct value *function,
>  		{
>  		  convert_typed_floating ((const bfd_byte *) writebuf +
>  					  i * (TYPE_LENGTH (valtype) / 2),
> -					  valtype, regval, regtype);
> +					  TYPE_TARGET_TYPE (valtype), regval,
> +					  regtype);
>  		  regcache_cooked_write (regcache,
>                                           tdep->ppc_fp0_regnum + 1 + i,
>  					 regval);
> @@ -1938,7 +1939,7 @@ ppc64_sysv_abi_return_value (struct gdbarch *gdbarch, struct value *function,
>  		  convert_typed_floating (regval, regtype,
>  					  (bfd_byte *) readbuf +
>  					  i * (TYPE_LENGTH (valtype) / 2),
> -					  valtype);
> +					  TYPE_TARGET_TYPE (valtype));
>  		}
>  	    }
>  	}

OK for commit.

You could also replace TYPE_LENGTH (valtype) / 2 there
by TYPE_LENGTH (TYPE_TARGET_TYPE (valtype)) to make it more clear
(use some variable for TYPE_TARGET_TYPE (valtype); not required.


Thanks,
Jan


  reply	other threads:[~2012-11-26  9:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-17 16:01 Tiago Stürmer Daitx
2012-11-26  9:44 ` Jan Kratochvil [this message]
2013-01-23 18:37 Tiago Stürmer Daitx
2013-01-23 19:29 ` Ulrich Weigand
2013-01-23 20:04   ` Sergio Durigan Junior

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=20121126094346.GA12249@host2.jankratochvil.net \
    --to=jan.kratochvil@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