public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
To: Gabriel Dos Reis <gdr@codesourcery.com>
Cc: Mark Mitchell <mark@codesourcery.com>,
	gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org
Subject: Re: V3 PATCH: Fix PR3988
Date: Tue, 14 Aug 2001 14:59:00 -0000	[thread overview]
Message-ID: <e90925a91140872b3f36f0ec8efb7223@NO-ID-FOUND.mhonarc.org> (raw)
In-Reply-To: <fl66bqqpev.fsf@pizza.cmla.ens-cachan.fr>

On Tuesday 14 August 2001 23:53, Gabriel Dos Reis wrote:
> Franz Sirl <Franz.Sirl-kernel@lauterbach.com> writes:
> | On Tuesday 14 August 2001 00:24, Mark Mitchell wrote:
> | > The new limits stuff was accidentally thinking that the x86 had a long
> | > double type with 128 bits of precision, when really the precision is
> | > 80 bits.  Here's the fix.
> | >
> | > Tested on i686-pc-linux-gnu, installed on the branch and on the
> | > mainline.
> |
> | Hmm, don't we need the same stuff for powerpc too? AFAIK long double ==
> | double still on PPC, so __glibcpp_long_double_bits has to be set to 64.
> | This happens for powerpc64 (in config/os/gnu-linux/bits/os_defines.h),
> | but not for powerpc.
>
> Would you mind to provide a patch that defines the correct size?

Well, a patch for config/os/gnu-linux/bits/os_defines.h or a solution like 
the 386 one that Mark did?

Franz.

  reply	other threads:[~2001-08-14 14:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-13 15:24 Mark Mitchell
2001-08-14 14:46 ` Franz Sirl
     [not found] ` <200108142147.XAA20070@mayo.cmla.ens-cachan.fr>
2001-08-14 14:53   ` Gabriel Dos Reis
2001-08-14 14:59     ` Franz Sirl [this message]
2001-08-14 14:59 Mark Mitchell
2001-08-14 15:15 Mark Mitchell
2001-08-14 16:03 ` Benjamin Kosnik

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=e90925a91140872b3f36f0ec8efb7223@NO-ID-FOUND.mhonarc.org \
    --to=franz.sirl-kernel@lauterbach.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdr@codesourcery.com \
    --cc=libstdc++@gcc.gnu.org \
    --cc=mark@codesourcery.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).