public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
* Re: libstdc++/6553: 26_numerics/complex_inserters_extractors.cc fails in Tru64 UNIX V5.1
@ 2003-01-15 14:53 bangerth
0 siblings, 0 replies; 6+ messages in thread
From: bangerth @ 2003-01-15 14:53 UTC (permalink / raw)
To: bkoz, gcc-bugs, gcc-prs, ro
Synopsis: 26_numerics/complex_inserters_extractors.cc fails in Tru64 UNIX V5.1
State-Changed-From-To: open->closed
State-Changed-By: bangerth
State-Changed-When: Wed Jan 15 06:53:37 2003
State-Changed-Why:
Fixed
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6553
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: libstdc++/6553: 26_numerics/complex_inserters_extractors.cc fails in Tru64 UNIX V5.1
@ 2003-01-15 11:26 Rainer Orth
0 siblings, 0 replies; 6+ messages in thread
From: Rainer Orth @ 2003-01-15 11:26 UTC (permalink / raw)
To: bkoz; +Cc: gcc-prs
The following reply was made to PR libstdc++/6553; it has been noted by GNATS.
From: Rainer Orth <ro@TechFak.Uni-Bielefeld.DE>
To: bangerth@dealii.org, bkoz@gcc.gnu.org, gcc-bugs@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, 15 Jan 2003 12:16:57 +0100 (MET)
bangerth@dealii.org writes:
> Synopsis: 26_numerics/complex_inserters_extractors.cc fails in Tru64 UNIX V5.1
>
> State-Changed-From-To: feedback->open
> State-Changed-By: bangerth
> State-Changed-When: Tue Jan 14 14:59:10 2003
> State-Changed-Why:
> Feedback provided a long time ago. I think the libstdc++
> people would need to go over this again...
This bug has already been fixed for the 3.2 branch and up by this patch:
http://gcc.gnu.org/ml/gcc-patches/2002-08/msg00229.html
http://gcc.gnu.org/ml/gcc-patches/2002-09/msg00366.html
Rainer
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: libstdc++/6553: 26_numerics/complex_inserters_extractors.cc fails in Tru64 UNIX V5.1
@ 2003-01-14 22:59 bangerth
0 siblings, 0 replies; 6+ messages in thread
From: bangerth @ 2003-01-14 22:59 UTC (permalink / raw)
To: bkoz, gcc-bugs, gcc-prs, ro
Synopsis: 26_numerics/complex_inserters_extractors.cc fails in Tru64 UNIX V5.1
State-Changed-From-To: feedback->open
State-Changed-By: bangerth
State-Changed-When: Tue Jan 14 14:59:10 2003
State-Changed-Why:
Feedback provided a long time ago. I think the libstdc++
people would need to go over this again...
W.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6553
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: libstdc++/6553: 26_numerics/complex_inserters_extractors.cc fails in Tru64 UNIX V5.1
@ 2002-05-29 3:36 Rainer Orth
0 siblings, 0 replies; 6+ messages in thread
From: Rainer Orth @ 2002-05-29 3:36 UTC (permalink / raw)
To: bkoz; +Cc: gcc-prs
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: libstdc++/6553: 26_numerics/complex_inserters_extractors.cc fails in Tru64 UNIX V5.1
@ 2002-05-29 2:29 bkoz
0 siblings, 0 replies; 6+ messages in thread
From: bkoz @ 2002-05-29 2:29 UTC (permalink / raw)
To: bkoz, gcc-bugs, gcc-prs, nobody, ro
Synopsis: 26_numerics/complex_inserters_extractors.cc fails in Tru64 UNIX V5.1
Responsible-Changed-From-To: unassigned->bkoz
Responsible-Changed-By: bkoz
Responsible-Changed-When: Wed May 29 02:26:09 2002
Responsible-Changed-Why:
Mine.
State-Changed-From-To: open->feedback
State-Changed-By: bkoz
State-Changed-When: Wed May 29 02:26:09 2002
State-Changed-Why:
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.
best,
benjamin
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6553
^ permalink raw reply [flat|nested] 6+ messages in thread
* libstdc++/6553: 26_numerics/complex_inserters_extractors.cc fails in Tru64 UNIX V5.1
@ 2002-05-03 14:26 Rainer Orth
0 siblings, 0 replies; 6+ messages in thread
From: Rainer Orth @ 2002-05-03 14:26 UTC (permalink / raw)
To: gcc-gnats
>Number: 6553
>Category: libstdc++
>Synopsis: 26_numerics/complex_inserters_extractors.cc fails in Tru64 UNIX V5.1
>Confidential: no
>Severity: critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: wrong-code
>Submitter-Id: net
>Arrival-Date: Fri May 03 14:26:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator: Rainer Orth
>Release: 3.1 20020426 (prerelease)
>Organization:
Faculty of Technology, Bielefeld University
>Environment:
System: OSF1 bartok V5.1 732 alpha
Machine: alpha
host: alpha-dec-osf5.1
build: alpha-dec-osf5.1
target: alpha-dec-osf5.1
configured with: /vol/gnu/src/gcc/gcc-3.1-branch-dist/configure --prefix=/vol/gcc --with-local-prefix=/vol/gcc --disable-nls alpha-dec-osf5.1
>Description:
Comparing testresults for Tru64 UNIX V4.0F
http://gcc.gnu.org/ml/gcc-testresults/2002-04/msg01129.html
and V5.1
http://gcc.gnu.org/ml/gcc-testresults/2002-04/msg01130.html
there's only a single difference: an additional failure in V5.1:
FAIL: 26_numerics/complex_inserters_extractors.cc execution test. In libstdc++.log,
I find
Assertion failed: flteq(z.imag(), y), file /amnt/zacatecas/volumes/d9/gnu/src/gcc/gcc-3.1-branch-dist/libstdc++-v3/testsuite/26_numerics/complex_inserters_extractors.cc, line 48
This is
VERIFY( flteq(z.imag(), y) );
the first long double invocation of test_good() with "(-1.1,3.7)#" as input
string, as can be seen in a stacktrace:
#6 0x12001c9a8 in _Z9test_goodIeEiSsT_S0_ (str={
static npos = <incomplete type>,
_M_dataplus = {<allocator<char>> = {<No data fields>},
_M_p = 0x14000c818 "(-1.1,3.7)#"}, static _S_empty_rep_storage = {0,
0, 0, 0}}, x=-1.1000000000000000888178419700125232,
y=3.7000000000000001776356839400250465)
at /vol/gnu/src/gcc/gcc-3.1-branch-dist/libstdc++-v3/testsuite/26_numerics/complex_inserters_extractors.cc:48
#7 0x120019304 in _Z7testallIeEiv ()
at /vol/gnu/src/gcc/gcc-3.1-branch-dist/libstdc++-v3/testsuite/26_numerics/complex_inserters_extractors.cc:74
#8 0x12000e9cc in main ()
at /vol/gnu/src/gcc/gcc-3.1-branch-dist/libstdc++-v3/testsuite/26_numerics/complex_inserters_extractors.cc:139
139 testall<long double>();
Unfortunately, print z in gdb 5.2 just yields
$2 = {_M_value = Invalid C/C++ type code 20 in symbol table.
so I cannot easily debug this further.
Since this is a long double test failing and a primary difference between
V4.0F and V5.1 is the support for 128-bit long double, this might well be
related to problems with long double argument passing.
>How-To-Repeat:
Bootstrap compiler and run testsuite.
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2003-01-15 14:53 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-01-15 14:53 libstdc++/6553: 26_numerics/complex_inserters_extractors.cc fails in Tru64 UNIX V5.1 bangerth
-- strict thread matches above, loose matches on Subject: below --
2003-01-15 11:26 Rainer Orth
2003-01-14 22:59 bangerth
2002-05-29 3:36 Rainer Orth
2002-05-29 2:29 bkoz
2002-05-03 14:26 Rainer Orth
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).