From: Michael Snyder <msnyder@redhat.com>
To: Richard.Earnshaw@arm.com
Cc: Fernando Nasser <fnasser@redhat.com>,
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, 07 Jan 2003 23:46:00 -0000 [thread overview]
Message-ID: <3E1B66BC.B5D75FEA@redhat.com> (raw)
In-Reply-To: <200212041002.gB4A27w05408@pc960.cambridge.arm.com>
[-- Attachment #1: Type: text/plain, Size: 632 bytes --]
Richard Earnshaw wrote:
>
> fnasser@redhat.com said:
> > 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?
>
> No. In this case we really need to copy the least significant 1 (or 2)
> bytes into the 1 or 2 bytes in the valbuf target. That means doing a copy
> from the higher addresses. So in that respect, the patch is correct.
>
> But it breaks the case where the return value is more than one word.
Yes, I see that now. Richard, how about a joint effort?
Would you be so kind as to fill in the empty else clause?
[-- Attachment #2: arm.diff --]
[-- Type: text/plain, Size: 793 bytes --]
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 7 Jan 2003 23:45:19 -0000
*************** arm_extract_return_value (struct type *t
*** 2274,2279 ****
--- 2274,2292 ----
break;
}
}
+ else if (TARGET_BYTE_ORDER == BFD_ENDIAN_BIG)
+ {
+ if (TYPE_LENGTH (type) <= REGISTER_SIZE)
+ {
+ memcpy (valbuf,
+ ®buf[REGISTER_BYTE (ARM_A1_REGNUM)]
+ + (REGISTER_RAW_SIZE (ARM_A1_REGNUM) - TYPE_LENGTH (type)),
+ TYPE_LENGTH (type));
+ }
+ else
+ {
+ }
+ }
else
memcpy (valbuf, ®buf[REGISTER_BYTE (ARM_A1_REGNUM)],
TYPE_LENGTH (type));
next prev parent reply other threads:[~2003-01-07 23:46 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
2002-12-04 2:02 ` Richard Earnshaw
2003-01-07 23:46 ` Michael Snyder [this message]
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=3E1B66BC.B5D75FEA@redhat.com \
--to=msnyder@redhat.com \
--cc=Richard.Earnshaw@arm.com \
--cc=cagney@redhat.com \
--cc=fnasser@redhat.com \
--cc=fnasser@tooth.toronto.redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kevinb@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