This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: libstdc++/6553: 26_numerics/complex_inserters_extractors.cc fails in Tru64 UNIX V5.1
- From: Rainer Orth <ro at TechFak dot Uni-Bielefeld dot DE>
- To: bkoz at gcc dot gnu dot org, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, nobody at gcc dot gnu dot org, gcc-gnats at gcc dot gnu dot org
- Date: Wed, 29 May 2002 12:04:01 +0200 (MEST)
- Subject: Re: libstdc++/6553: 26_numerics/complex_inserters_extractors.cc fails in Tru64 UNIX V5.1
- References: <20020529092611.14911.qmail@sources.redhat.com>
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