From: Jerome Guitton <guitton@act-europe.fr>
To: gdb-patches@sources.redhat.com
Subject: [RFA] powerpc - extract a float return value
Date: Tue, 20 Apr 2004 18:03:00 -0000 [thread overview]
Message-ID: <20040420180348.GA23715@act-europe.fr> (raw)
[-- Attachment #1: Type: text/plain, Size: 607 bytes --]
Hello GDB folks,
The way GDB extracts float return values in rs6000-tdep.c
(rs6000_extract_return_value) seems dubious to me:
[...]
memcpy (&dd, ®buf[DEPRECATED_REGISTER_BYTE (FP0_REGNUM + 1)], 8);
ff = (float) dd;
memcpy (valbuf, &ff, sizeof (float));
[...]
The cast will not work properly if the target and the host have not a similar
float representation.
I propose to fix that by a call to convert_typed_floating. See patch in
attachment.
I have not yet tested it against the testsuite, I will do that
tomorrow. In the meantime, if you have comments I would be happy to
address them!
--
Jerome
[-- Attachment #2: diff.2 --]
[-- Type: text/plain, Size: 1301 bytes --]
2004-04-20 Jerome Guitton <guitton@gnat.fr>
* rs6000-tdep.c (rs6000_extract_return_value): When extracting a float,
use convert_typed_floating to get the appropriate format.
Index: rs6000-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/rs6000-tdep.c,v
retrieving revision 1.191
diff -u -p -r1.191 rs6000-tdep.c
--- rs6000-tdep.c 1 Apr 2004 21:00:59 -0000 1.191
+++ rs6000-tdep.c 20 Apr 2004 17:45:24 -0000
@@ -1251,8 +1251,6 @@ rs6000_extract_return_value (struct type
if (TYPE_CODE (valtype) == TYPE_CODE_FLT)
{
- double dd;
- float ff;
/* floats and doubles are returned in fpr1. fpr's have a size of 8 bytes.
We need to truncate the return value into float size (4 byte) if
necessary. */
@@ -1263,9 +1261,11 @@ rs6000_extract_return_value (struct type
TYPE_LENGTH (valtype));
else
{ /* float */
- memcpy (&dd, ®buf[DEPRECATED_REGISTER_BYTE (FP0_REGNUM + 1)], 8);
- ff = (float) dd;
- memcpy (valbuf, &ff, sizeof (float));
+ convert_typed_floating (®buf[DEPRECATED_REGISTER_BYTE
+ (FP0_REGNUM + 1)],
+ builtin_type_double,
+ valbuf,
+ valtype);
}
}
else if (TYPE_CODE (valtype) == TYPE_CODE_ARRAY
next reply other threads:[~2004-04-20 18:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-20 18:03 Jerome Guitton [this message]
2004-04-21 17:54 ` Kevin Buettner
2004-04-21 19:40 ` Andrew Cagney
2004-04-23 14:38 ` Jerome Guitton
2004-04-23 16:03 ` Kevin Buettner
2004-04-23 16:23 ` Jerome Guitton
2004-04-24 0:03 ` Andrew Cagney
2004-04-23 16:39 ` Jerome Guitton
2004-04-23 19:14 ` Joel Brobecker
2004-04-24 0:03 ` Andrew Cagney
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=20040420180348.GA23715@act-europe.fr \
--to=guitton@act-europe.fr \
--cc=gdb-patches@sources.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