public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "danglin at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/35838]  New: FAIL: 22_locale/num_get/get/char/16.cc execution test, and 76 others
Date: Sat, 05 Apr 2008 23:20:00 -0000	[thread overview]
Message-ID: <bug-35838-276@http.gcc.gnu.org/bugzilla/> (raw)

Executing on host: /test/gnu/gcc/objdir/./gcc/g++ -shared-libgcc
-B/test/gnu/gcc
/objdir/./gcc -nostdinc++
-L/test/gnu/gcc/objdir/hppa2.0w-hp-hpux11.11/libstdc++
-v3/src -L/test/gnu/gcc/objdir/hppa2.0w-hp-hpux11.11/libstdc++-v3/src/.libs
-B/o
pt/gnu/gcc/gcc-4.4.0/hppa2.0w-hp-hpux11.11/bin/
-B/opt/gnu/gcc/gcc-4.4.0/hppa2.0
w-hp-hpux11.11/lib/ -isystem
/opt/gnu/gcc/gcc-4.4.0/hppa2.0w-hp-hpux11.11/includ
e -isystem /opt/gnu/gcc/gcc-4.4.0/hppa2.0w-hp-hpux11.11/sys-include -g -O2
-D_GL
IBCXX_ASSERT -fmessage-length=0 -g -O2 -g -O2   -DLOCALEDIR="." -nostdinc++
-I/t
est/gnu/gcc/objdir/hppa2.0w-hp-hpux11.11/libstdc++-v3/include/hppa2.0w-hp-hpux11
.11 -I/test/gnu/gcc/objdir/hppa2.0w-hp-hpux11.11/libstdc++-v3/include
-I/test/gn
u/gcc/gcc/libstdc++-v3/libsupc++
-I/test/gnu/gcc/gcc/libstdc++-v3/include/backwa
rd -I/test/gnu/gcc/gcc/libstdc++-v3/testsuite/util
/test/gnu/gcc/gcc/libstdc++-v
3/testsuite/22_locale/num_get/get/char/16.cc    -include bits/stdc++.h
./libtest
c++.a  -lm   -o ./16.exe    (timeout = 600)
PASS: 22_locale/num_get/get/char/16.cc (test for excess errors)
Setting LD_LIBRARY_PATH to
:/test/gnu/gcc/objdir/gcc:/test/gnu/gcc/objdir/hppa2.
0w-hp-hpux11.11/./libstdc++-v3/src/.libs::/test/gnu/gcc/objdir/gcc:/test/gnu/gcc
/objdir/hppa2.0w-hp-hpux11.11/./libstdc++-v3/src/.libs
Assertion failed: err == ios_base::eofbit, file
/test/gnu/gcc/gcc/libstdc++-v3/t
estsuite/22_locale/num_get/get/char/16.cc, line 57
FAIL: 22_locale/num_get/get/char/16.cc execution test

These failures were introduced between 133450 and 133543.


-- 
           Summary: FAIL: 22_locale/num_get/get/char/16.cc execution test,
                    and 76 others
           Product: gcc
           Version: 4.4.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: danglin at gcc dot gnu dot org
 GCC build triplet: hppa*-*-*
  GCC host triplet: hppa*-*-*
GCC target triplet: hppa*-*-*


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35838


             reply	other threads:[~2008-04-05 23:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-05 23:20 danglin at gcc dot gnu dot org [this message]
2008-04-06 16:28 ` [Bug c++/35838] " danglin at gcc dot gnu dot org
2008-04-09 14:14 ` danglin at gcc dot gnu dot org
2008-04-12 22:23 ` danglin at gcc dot gnu dot org
2008-04-12 22:35 ` [Bug middle-end/35838] [4.4 Regression] " pinskia at gcc dot gnu dot org
2008-04-13 14:10 ` dave at hiauly1 dot hia dot nrc dot ca
2008-04-14 11:28 ` rsandifo at gcc dot gnu dot org
2008-04-15 15:38 ` dave at hiauly1 dot hia dot nrc dot ca
2008-04-17 20:21 ` rsandifo at gcc dot gnu dot org
2008-04-17 20:22 ` [Bug rtl-optimization/35838] " rsandifo at gcc dot gnu dot org

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=bug-35838-276@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).