public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Rainer Orth <ro@TechFak.Uni-Bielefeld.DE>
To: bkoz@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: libstdc++/6553: 26_numerics/complex_inserters_extractors.cc fails in Tru64 UNIX V5.1
Date: Wed, 29 May 2002 03:36:00 -0000	[thread overview]
Message-ID: <20020529100604.30459.qmail@sources.redhat.com> (raw)

The following reply was made to PR libstdc++/6553; it has been noted by GNATS.

From: Rainer Orth <ro@TechFak.Uni-Bielefeld.DE>
To: bkoz@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
        nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: libstdc++/6553: 26_numerics/complex_inserters_extractors.cc fails in Tru64 UNIX V5.1
Date: Wed, 29 May 2002 12:04:01 +0200 (MEST)

 bkoz@gcc.gnu.org writes:
 
 >     Hi! Hey, I think the fix to this is pretty simple:
 >     
 >     libstdc++-v3/config/os/osf/osf5.0/bits/cpu_limits.h
 >     
 >     has:
 >     
 >     #define __glibcpp_long_bits 64
 >     
 >     #define __glibcpp_long_double_bits 128
 >     
 >     So, to get this working, don't you just have to add an OSF 4.0 config that doesn't have these defines?
 >     
 >     Seems pretty simple, if this is it.
 
 I don't think so: these values are only used on Tru64 UNIX V5.x, as can be
 seen in configure.target:
 
    alpha*-*-*osf5*)
      CPULIMITSH=config/os/osf/osf5.0
 
 V4.0 uses this instead
 
    alpha*-*-*)
      CPULIMITSH=config/cpu/alpha
 
 which has the correct
 
 #define __glibcpp_long_bits 64
 #define __glibcpp_long_double_bits 64
 
 since 128-bit long double support was only introduced (via software
 emulation) in V5.  So, despite __glibcpp_long_double_bits is correct for
 both V4.0 and V5.1, the testcase fails in V5.1.
 
 	Rainer


             reply	other threads:[~2002-05-29 10:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-29  3:36 Rainer Orth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-15 14:53 bangerth
2003-01-15 11:26 Rainer Orth
2003-01-14 22:59 bangerth
2002-05-29  2:29 bkoz
2002-05-03 14:26 Rainer Orth

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=20020529100604.30459.qmail@sources.redhat.com \
    --to=ro@techfak.uni-bielefeld.de \
    --cc=bkoz@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    /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).