From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13192 invoked by alias); 11 Jun 2003 19:01:08 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 13108 invoked from network); 11 Jun 2003 19:01:07 -0000 Received: from unknown (HELO walton.kettenis.dyndns.org) (62.163.169.212) by sources.redhat.com with SMTP; 11 Jun 2003 19:01:07 -0000 Received: from elgar.kettenis.dyndns.org (elgar.kettenis.dyndns.org [192.168.0.2]) by walton.kettenis.dyndns.org (8.12.6p2/8.12.5) with ESMTP id h5BJ10N1000257; Wed, 11 Jun 2003 21:01:00 +0200 (CEST) (envelope-from kettenis@elgar.kettenis.dyndns.org) Received: from elgar.kettenis.dyndns.org (localhost [127.0.0.1]) by elgar.kettenis.dyndns.org (8.12.6p2/8.12.6) with ESMTP id h5BJ0xVh000381; Wed, 11 Jun 2003 21:00:59 +0200 (CEST) (envelope-from kettenis@elgar.kettenis.dyndns.org) Received: (from kettenis@localhost) by elgar.kettenis.dyndns.org (8.12.6p2/8.12.6/Submit) id h5BJ0xmW000378; Wed, 11 Jun 2003 21:00:59 +0200 (CEST) To: Jim Blandy Cc: gdb-patches@sources.redhat.com Subject: Re: [ppc64-linux]: specify size of long double on PPC64 Linux References: From: Mark Kettenis Date: Wed, 11 Jun 2003 19:01:00 -0000 In-Reply-To: Jim Blandy's message of "11 Jun 2003 02:50:42 -0500" Message-ID: <86n0go8mms.fsf@elgar.kettenis.dyndns.org> X-SW-Source: 2003-06/txt/msg00376.txt.bz2 Jim Blandy writes: > 2003-06-11 Jim Blandy > > * 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); It's probably a matter of taste, but I'd use the plain number 128 here instead of expressing things in TARGET_CHAR_BIT. Mark