From: Fernando Nasser <fnasser@redhat.com>
To: Michael Snyder <msnyder@redhat.com>
Cc: gdb-patches@sources.redhat.com, rearnsha@arm.com,
cagney@redhat.com, kevinb@redhat.com,
fnasser <fnasser@tooth.toronto.redhat.com>
Subject: Re: [RFA] arm_extract_return_value, big-endian
Date: Tue, 03 Dec 2002 07:41:00 -0000 [thread overview]
Message-ID: <3DECD32C.2050403@redhat.com> (raw)
In-Reply-To: <3DC989E0.DCFDC68A@redhat.com>
Humm..., I am having second thoughts about this. Isn't the problem you
are seeing the same problem of not having the values peoperly
sign-extended? I guess I will have to look into this closer (and my ARM
manuals are not here right now either).
Please do not apply the patch yet Michael. Sorry,. :-(
Fernando
Michael Snyder wrote:
> [This doesn't seem to have gone out. Excuse me if it appears twice]
>
> One of you arm-savvy guys check me out on this:
> it seems logical, and it fixes two fails in callfuncs with -mbig-endian.
>
> Michael
>
>
> ------------------------------------------------------------------------
>
> 2002-11-05 Michael Snyder <msnyder@redhat.com>
>
> * arm-tdep.c (arm_extract_return_value): Handle offset of
> small types on big-endian machines.
>
> Index: arm-tdep.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/arm-tdep.c,v
> retrieving revision 1.74
> diff -p -r1.74 arm-tdep.c
> *** arm-tdep.c 1 Nov 2002 21:21:49 -0000 1.74
> --- arm-tdep.c 6 Nov 2002 01:54:36 -0000
> *************** arm_extract_return_value (struct type *t
> *** 2274,2279 ****
> --- 2274,2284 ----
> break;
> }
> }
> + else if (TARGET_BYTE_ORDER == BFD_ENDIAN_BIG)
> + memcpy (valbuf,
> + ®buf[REGISTER_BYTE (ARM_A1_REGNUM)]
> + + (REGISTER_RAW_SIZE (ARM_A1_REGNUM) - TYPE_LENGTH (type)),
> + TYPE_LENGTH (type));
> else
> memcpy (valbuf, ®buf[REGISTER_BYTE (ARM_A1_REGNUM)],
> TYPE_LENGTH (type));
--
Fernando Nasser
Red Hat Canada Ltd. E-Mail: fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario M4P 2C9
next prev parent reply other threads:[~2002-12-03 15:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-06 13:30 Michael Snyder
2002-12-03 7:33 ` Fernando Nasser
2002-12-03 7:41 ` Fernando Nasser [this message]
2002-12-04 2:02 ` Richard Earnshaw
2003-01-07 23:46 ` Michael Snyder
2003-01-08 9:48 ` Richard Earnshaw
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=3DECD32C.2050403@redhat.com \
--to=fnasser@redhat.com \
--cc=cagney@redhat.com \
--cc=fnasser@tooth.toronto.redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kevinb@redhat.com \
--cc=msnyder@redhat.com \
--cc=rearnsha@arm.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