From: Thomas Weise <tom@zaphod.wh9.tu-dresden.de>
To: law@cygnus.com
Cc: Jason Merrill <jason@cygnus.com>,
Theodore Papadopoulo <Theodore.Papadopoulo@sophia.inria.fr>,
egcs@cygnus.com
Subject: Re: results egcs-1.0: i586-pc-linux-gnulibc1 (S.u.S.E.4.4.1)
Date: Sun, 07 Dec 1997 12:51:00 -0000 [thread overview]
Message-ID: <348B1973.1B1F@zaphod.wh9.tu-dresden.de> (raw)
In-Reply-To: <28273.881428539@hurl.cygnus.com>
Jeffrey A Law wrote:
> The g++ failures are due to a bug in the testing harness; it's not
> arranging for the test programs to find the freshly built shared C++
> libs, instead they pick up whatever shared versions of the C++ libs
> it can find in the standard locations on your system.
Exactly. LD_LIBRARY_PATH hasn't been set and an old libstdc++.so was as
well lying around in /usr/lib. Sorry for any confusion my report may
have caused. Results below are as expected.
tom.
S.u.S.E. Linux 4.4.1 + binutils-2.8.1.0.15 + libc-5.4.39
configure --enable-shared
Test Run By tom on Sun Dec 7 18:27:26 1997
Native configuration is i486-pc-linux-gnulibc1
=== libio tests ===
=== libio Summary ===
# of expected passes 40
Test Run By tom on Sun Dec 7 18:30:26 1997
Native configuration is i486-pc-linux-gnulibc1
=== libstdc++ tests ===
=== libstdc++ Summary ===
# of expected passes 30
Test Run By tom on Sun Dec 7 18:33:25 1997
Native configuration is i486-pc-linux-gnulibc1
=== gcc tests ===
=== gcc Summary ===
# of expected passes 4883
# of expected failures 5
# of unsupported tests 7
/home/tom/egcs-1.0/gcc/xgcc version egcs-2.90.21 971202 (egcs-1.00
release)
=== g++ tests ===
XPASS: g++.jason/destruct3.C - (test for bogus messages, line 38)
XPASS: g++.mike/dyncast1.C Execution test
XPASS: g++.mike/dyncast2.C Execution test
=== g++ Summary ===
# of expected passes 3400
# of unexpected successes 3
# of expected failures 80
# of untested testcases 6
/home/tom/egcs-1.0/gcc/testsuite/../xgcc version egcs-2.90.21 971202
(egcs-1.00 release)
Test Run By tom on Sun Dec 7 19:59:26 1997
Native configuration is i486-pc-linux-gnulibc1
=== g77 tests ===
FAIL: g77.f-torture/execute/dnrm2.f execution, -O2 -fomit-frame-pointer
-finline-functions -funroll-loops
FAIL: g77.f-torture/execute/dnrm2.f execution, -O2 -fomit-frame-pointer
-finline-functions -funroll-all-loops
=== g77 Summary ===
# of expected passes 130
# of unexpected failures 2
/home/tom/egcs-1.0/gcc/g77 version egcs-2.90.21 971202 (egcs-1.00
release)
--
Thomas Weise, http://www.inf.tu-dresden.de/~tw4
Dresden University of Technology, Department of Computer Science
next prev parent reply other threads:[~1997-12-07 12:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-05 13:11 No Subject Thomas Weise
1997-12-06 9:23 ` Jeffrey A Law
1997-12-07 12:51 ` Thomas Weise [this message]
1997-12-05 14:00 results egcs-1.0: i586-pc-linux-gnulibc1 (S.u.S.E.4.4.1) Thomas Weise
1997-12-05 15:37 ` H.J. Lu
[not found] <199712051824.TAA09338.cygnus.egcs@zaphod.wh9.tu-dresden.de>
1997-12-05 16:12 ` Jason Merrill
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=348B1973.1B1F@zaphod.wh9.tu-dresden.de \
--to=tom@zaphod.wh9.tu-dresden.de \
--cc=Theodore.Papadopoulo@sophia.inria.fr \
--cc=egcs@cygnus.com \
--cc=jason@cygnus.com \
--cc=law@cygnus.com \
/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).