From: Jim Blandy <jimb@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: RFA: correct size of long double on PPC Linux
Date: Wed, 24 Mar 2004 18:10:00 -0000 [thread overview]
Message-ID: <vt2u10ew1ye.fsf@zenia.home> (raw)
2004-03-24 Jim Blandy <jimb@redhat.com>
* ppc-linux-tdep.c (ppc_linux_init_abi): Long doubles are eight
bytes long on PPC Linux.
Index: gdb/ppc-linux-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/ppc-linux-tdep.c,v
retrieving revision 1.49
diff -c -r1.49 ppc-linux-tdep.c
*** gdb/ppc-linux-tdep.c 14 Nov 2003 14:16:29 -0000 1.49
--- gdb/ppc-linux-tdep.c 11 Feb 2004 18:59:31 -0000
***************
*** 1042,1047 ****
--- 1042,1049 ----
if (tdep->wordsize == 4)
{
+ set_gdbarch_long_double_bit (gdbarch, 8 * TARGET_CHAR_BIT);
+
/* Until November 2001, gcc did not comply with the 32 bit SysV
R4 ABI requirement that structures less than or equal to 8
bytes should be returned in registers. Instead GCC was using
next reply other threads:[~2004-03-24 18:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-24 18:10 Jim Blandy [this message]
2004-03-26 14:12 ` Kevin Buettner
2004-03-26 15:19 ` Daniel Jacobowitz
2004-03-26 15:45 ` Jim Blandy
2004-03-26 16:23 ` Kevin Buettner
2004-03-26 21:05 ` Jim Blandy
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=vt2u10ew1ye.fsf@zenia.home \
--to=jimb@redhat.com \
--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