public inbox for
help / color / mirror / Atom feed
Subject: libstdc++/10809: [3.3 regression] mips-sgi-irix6.5 libstdc++-v3 testsuite execution failure in 27_io/
Date: Fri, 16 May 2003 01:46:00 -0000	[thread overview]
Message-ID: <> (raw)

>Number:         10809
>Category:       libstdc++
>Synopsis:       [3.3 regression] mips-sgi-irix6.5 libstdc++-v3 testsuite execution failure in 27_io/
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          wrong-code
>Submitter-Id:   net
>Arrival-Date:   Fri May 16 01:46:00 UTC 2003
>Originator:     Kaveh Ghazi
>Release:        gcc 3.3 (release)
I noticed that there is a testsuite regression on irix6 in 27_io/  See:

Looking back through the testresult archives, it looks like the regression appeared around two weeks ago in the May 2nd snapshot.
May 1:
May 2:

It's an execution failure.  Running the binary I get:

Assertion failed: EX, file /caip/u58/ghazi/gcc-testing/branch/gcc-3.3/libstdc++-v3/testsuite/27_io/, line 606

Unfortunately I can't make sense of why it does this though.
It's an execute failure, compile and run 27_io/  In my tree the command line to build it was the following, but it's very path dependent so you'll probably have to run the libstdc++-v3 testsuite on irix6 yourself:

/caip/u58/ghazi/gcc-testing/branch/build/gcc/g++ -shared-libgcc -B/caip/u58/ghazi/gcc-testing/branch/build/gcc/ -nostdinc++ -L/caip/u58/ghazi/gcc-testing/branch/build/mips-sgi-irix6.5/libstdc++-v3/src -L/caip/u58/ghazi/gcc-testing/branch/build/mips-sgi-irix6.5/libstdc++-v3/src/.libs -B/usr/local/mips-sgi-irix6.5/bin/ -B/usr/local/mips-sgi-irix6.5/lib/ -isystem /usr/local/mips-sgi-irix6.5/include -g -ffunction-sections -fdata-sections -fmessage-length=0 -DDEBUG_ASSERT -DLOCALEDIR="/caip/u58/ghazi/gcc-testing/branch/build/mips-sgi-irix6.5/libstdc++-v3/po/share/locale" -nostdinc++ -I/caip/u58/ghazi/gcc-testing/branch/build/mips-sgi-irix6.5/libstdc++-v3/include/mips-sgi-irix6.5 -I/caip/u58/ghazi/gcc-testing/branch/build/mips-sgi-irix6.5/libstdc++-v3/include -I/caip/u58/ghazi/gcc-testing/branch/gcc-3.3/libstdc++-v3/libsupc++ -I/caip/u58/ghazi/gcc-testing/branch/gcc-3.3/libstdc++-v3/libio -I/caip/u58/ghazi/gcc-testing/branch/gcc-3.3/libstdc++-v3/include/backward -I/caip/u58/ghazi/gcc-testing/branch/gcc-3.3/libstdc++-v3/testsuite /caip/u58/ghazi/gcc-testing/branch/gcc-3.3/libstdc++-v3/testsuite/27_io/ -g -O2 -DDEBUG_ASSERT -lv3test -L/caip/u58/ghazi/gcc-testing/branch/build/mips-sgi-irix6.5//libstdc++-v3/testsuite -lm -o ./istream_unformatted.exe


             reply	other threads:[~2003-05-16  1:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-16  1:46 ghazi [this message]
2003-05-16  7:36 Eric Botcazou
2003-05-16 17:25 paolo
2003-05-17 14:06 Eric Botcazou
2003-05-17 22:46 Paolo Carlini
2003-05-19  8:36 Eric Botcazou

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).