From: Richard Earnshaw <rearnsha@buzzard.freeserve.co.uk>
To: gdb-patches@sources.redhat.com
Cc: Richard.Earnshaw@buzzard.freeserve.co.uk,
Michael Snyder <msnyder@to-limbo.toronto.redhat.com>
Subject: ARM PATCH fix extract_return_value and store_return_value
Date: Sat, 14 Dec 2002 06:33:00 -0000 [thread overview]
Message-ID: <200212141048.gBEAm5e17339@buzzard.buzzard.freeserve.co.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1140 bytes --]
This patch cleans up the way the ARM tdep code handles extracting and
storing return values. Not only does it convert the methods to the new
regcache abstraction but it also fixes (at least I hope it fixes) the
big-endian problems that Michael was reporting on a big-endian ARM.
Michael, I've only run this through a little-endian testsuite. Could you
let me know if it solves the problems you were reporting.
R.
2002-12-14 Richard Earnshaw <rearnsha@arm.com>
* arm-tdep.c (convert_from_extended): New argument to hold the
type of floating point result we want to convert to. Make input
argument const. Fix all callers.
(convert_to_extended): Similarly.
(arm_extract_return_value): Now takes a regcache argument. Change
code to use regcache accessor functions. Correctly extract
smaller-than-word results on big-endian machines.
(arm_store_return_value): Now takes a regcache argument. Change
code to use regcache accessor functions. Correctly zero/sign extend
smaller than word results before storing into r0.
(arm_gdbarch_init): Register new-style extract_return_value and
store_return_value functions.
[-- Attachment #2: gdb-retval.patch --]
[-- Type: application/x-patch , Size: 10781 bytes --]
next reply other threads:[~2002-12-14 10:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-14 6:33 Richard Earnshaw [this message]
2003-01-24 3:10 ` Michael Snyder
2003-01-24 11:13 ` Richard Earnshaw
2003-01-24 19:45 ` Michael Snyder
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=200212141048.gBEAm5e17339@buzzard.buzzard.freeserve.co.uk \
--to=rearnsha@buzzard.freeserve.co.uk \
--cc=Richard.Earnshaw@buzzard.freeserve.co.uk \
--cc=gdb-patches@sources.redhat.com \
--cc=msnyder@to-limbo.toronto.redhat.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