From: Pierre Muller <muller@ics.u-strasbg.fr>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Support true 'long double' size.
Date: Tue, 11 Mar 2003 16:39:00 -0000 [thread overview]
Message-ID: <5.0.2.1.2.20030311173434.02b45028@ics.u-strasbg.fr> (raw)
In-Reply-To: <3E6DF2A2.8030609@redhat.com>
At 15:28 11/03/2003, Andrew Cagney wrote:
>>The old patch might still be usefull for other processors,
>>but I am not sure about that.
>
>We can wait until someone else reports a problem :-)
>
>>So here is a new simplified patch proposal:
>>ChangeLog entry:
>>2003-03-11 Pierre Muller <muller@ics.u-strasbg.fr>
>> * doublest.c (floatformat_from_length): Accept also
>> the real size of 'long double' type.
>>Index: doublest.c
>>===================================================================
>>RCS file: /cvs/src/src/gdb/doublest.c,v
>>retrieving revision 1.12
>>diff -p -u -r1.12 doublest.c
>>--- doublest.c 27 Feb 2003 18:08:25 -0000 1.12
>>+++ doublest.c 11 Mar 2003 12:17:52 -0000
>>@@ -633,6 +633,14 @@ floatformat_from_length (int len)
>> return TARGET_DOUBLE_FORMAT;
>> else if (len * TARGET_CHAR_BIT == TARGET_LONG_DOUBLE_BIT)
>> return TARGET_LONG_DOUBLE_FORMAT;
>>+ /* On i386 the 'long double' type takes 96 bits,
>>+ while the real number of used bits is only 80,
>>+ both in processor and in memory.
>>+ The code below accepts the real bit size. */
>>+ else if ((TARGET_LONG_DOUBLE_FORMAT)
>
>Yes, approved, just write the above as:
>
> (TARGET_LONG_DOUBLE_FORMAT != NULL)
Thanks, committed with the above change.
prev parent reply other threads:[~2003-03-11 16:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-17 16:54 [RFC] Support alternate " Pierre Muller
2003-02-18 19:46 ` Andrew Cagney
2003-03-11 12:21 ` [RFA] Support true " Pierre Muller
[not found] ` <3E6DF2A2.8030609@redhat.com>
2003-03-11 16:39 ` Pierre Muller [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=5.0.2.1.2.20030311173434.02b45028@ics.u-strasbg.fr \
--to=muller@ics.u-strasbg.fr \
--cc=ac131313@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