From: Jim Blandy <jimb@redhat.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [ppc64-linux]: specify size of long double on PPC64 Linux
Date: Thu, 12 Jun 2003 21:00:00 -0000 [thread overview]
Message-ID: <vt2llw7t3js.fsf@zenia.home> (raw)
In-Reply-To: <1030611191816.ZM26256@localhost.localdomain>
Kevin Buettner <kevinb@redhat.com> writes:
> On Jun 11, 2:50am, Jim Blandy wrote:
>
> > 2003-06-11 Jim Blandy <jimb@redhat.com>
> >
> > * ppc-linux-tdep.c (ppc_linux_init_abi): long doubles are 16 bytes
> > long.
> >
> > Index: gdb/ppc-linux-tdep.c
> > ===================================================================
> > RCS file: /cvs/src/src/gdb/ppc-linux-tdep.c,v
> > retrieving revision 1.28.8.13
> > diff -c -r1.28.8.13 ppc-linux-tdep.c
> > *** gdb/ppc-linux-tdep.c 10 Jun 2003 18:00:30 -0000 1.28.8.13
> > --- gdb/ppc-linux-tdep.c 11 Jun 2003 06:43:41 -0000
> > ***************
> > *** 1027,1032 ****
> > --- 1027,1034 ----
> >
> > if (tdep->wordsize == 8)
> > {
> > + set_gdbarch_long_double_bit (gdbarch, 16 * TARGET_CHAR_BIT);
> > +
> > set_gdbarch_call_dummy_address (gdbarch, ppc64_call_dummy_address);
> >
> > set_gdbarch_in_solib_call_trampoline
>
> Do you really need to do this?
>
> rs6000-tdep.c already has the following in it:
>
> if (sysv_abi)
> set_gdbarch_long_double_bit (gdbarch, 16 * TARGET_CHAR_BIT);
> else
> set_gdbarch_long_double_bit (gdbarch, 8 * TARGET_CHAR_BIT);
>
> So, if I'm not mistaken, the size of long doubles should already be
> set correctly.
Ach, yes, I read that backwards. Thanks for catching that.
prev parent reply other threads:[~2003-06-12 21:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-11 7:49 Jim Blandy
2003-06-11 19:01 ` Mark Kettenis
2003-06-11 19:18 ` Kevin Buettner
2003-06-12 21:00 ` Jim Blandy [this message]
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=vt2llw7t3js.fsf@zenia.home \
--to=jimb@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kevinb@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