public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: andreas.amann@gmx.de
To: gcc-gnats@gcc.gnu.org
Subject: libstdc++/10563: istream and locale: make check failures (regression from 3.2)
Date: Wed, 30 Apr 2003 11:26:00 -0000 [thread overview]
Message-ID: <20030430112256.2283.qmail@sources.redhat.com> (raw)
>Number: 10563
>Category: libstdc++
>Synopsis: istream and locale: make check failures (regression from 3.2)
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: wrong-code
>Submitter-Id: net
>Arrival-Date: Wed Apr 30 11:26:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator: Andreas Amann
>Release: gcc-3.2.3
>Organization:
>Environment:
> gcc -v
Reading specs from /usr/linux-local/gcc-3.2.3/lib/gcc-lib/i686-pc-linux-gnu/3.2.3/specs
Configured with: ../configure --prefix=/usr/linux-local/gcc-3.2.3 --with-local-prefix=/usr/linux-local
Thread model: posix
gcc version 3.2.3
>
System type: i686-pc-linux-gnu
glibc: 2.2.2
>Description:
I get unexpected failures in make check in libstdc++ with gcc-3.2.1 through gcc-3.2.3 (gcc-3.2.0 had no problems). The problem seems
to appear in tests related to "ctype". My locale setting is "C".
=== libstdc++-v3 tests ===
Running target unix
FAIL: 21_strings/inserters_extractors.cc execution test
FAIL: 22_locale/ctor_copy_dtor.cc execution test
XPASS: 22_locale/ctype_is_wchar_t.cc execution test
FAIL: 22_locale/ctype_scan_char.cc execution test
FAIL: 22_locale/ctype_to_char.cc execution test
FAIL: 22_locale/facet.cc execution test
XPASS: 22_locale/members.cc execution test
XPASS: 22_locale/messages_byname.cc execution test
XPASS: 22_locale/messages_members_char.cc execution test
XPASS: 22_locale/moneypunct_byname.cc execution test
XPASS: 22_locale/moneypunct_members_char.cc execution test
XPASS: 22_locale/moneypunct_members_wchar_t.cc execution test
XPASS: 22_locale/numpunct_byname.cc execution test
XPASS: 22_locale/numpunct_members_char.cc execution test
XPASS: 22_locale/numpunct_members_wchar_t.cc execution test
FAIL: 22_locale/operators.cc execution test
FAIL: 26_numerics/c99_classification_macros_c.cc (test for excess errors)
FAIL: 26_numerics/complex_inserters_extractors.cc execution test
FAIL: 27_io/istream_extractor_arith/01.cc execution test
FAIL: 27_io/istream_extractor_arith/07.cc execution test
FAIL: 27_io/istream_extractor_arith/08.cc execution test
FAIL: 27_io/istream_extractor_arith/09.cc execution test
FAIL: 27_io/istream_extractor_arith/10.cc execution test
FAIL: 27_io/istream_extractor_arith/11.cc execution test
FAIL: 27_io/istream_extractor_arith/12.cc execution test
FAIL: 27_io/istream_extractor_arith/13.cc execution test
FAIL: 27_io/istream_extractor_char.cc execution test
FAIL: 27_io/istream_manip.cc execution test
FAIL: 27_io/istream_sentry.cc execution test
FAIL: 27_io/ostream_inserter_arith.cc execution test
WARNING: program timed out.
FAIL: thread/pthread4.cc execution test
=== libstdc++-v3 Summary ===
# of expected passes 412
# of unexpected failures 21
# of unexpected successes 10
# of expected failures 16
Compiler version: 3.2.3
>How-To-Repeat:
../configure
make bootstrap && make -k check
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2003-04-30 11:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-30 11:26 andreas.amann [this message]
2003-04-30 12:01 paolo
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=20030430112256.2283.qmail@sources.redhat.com \
--to=andreas.amann@gmx.de \
--cc=gcc-gnats@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).