This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Report of current libstdc++-v3 testsuite results for *-*-freebsd4.2
- To: libstdc++ at gcc dot gnu dot org
- Subject: Report of current libstdc++-v3 testsuite results for *-*-freebsd4.2
- From: Loren James Rittle <rittle at latour dot rsch dot comm dot mot dot com>
- Date: Wed, 28 Mar 2001 18:00:04 -0600 (CST)
- Reply-to: rittle at rsch dot comm dot mot dot com
Over the past few days, things became quite unstable on *-*-freebsd4.2
on both 3.0 branch and mainline. Just as I was going to investigate,
patches appeared that restored order (and improved things on
alpha-*-freebsd* since the last time I studied the results closely).
I like it when that happens. ;-)
i386-unknown-freebsd4.2, on mainline: 106/6 shared + 106/6 static
i386-unknown-freebsd4.2, on 3.0 branch: 100/7 shared + 98/9 static
alpha-unknown-freebsd4.2, on 3.0 branch: 101/6 shared + 101/6 static
Exact failures (both static and dynamic unless annotated):
freebsd4.2 23_containers/map_operators.cc
freebsd4.2 23_containers/set_operators.cc
mainline 17_intro/header_csetjmp.cc
3.0 27_io/filebuf.cc
3.0 27_io/istream_seeks.cc
3.0 27_io/ios_base_members_static.cc
3.0 27_io/istream_extractor_char.cc
i386 21_strings/ctor_copy_dtor.cc
i386 21_strings/insert.cc (static only on 3.0, both on mainline)
i386 27_io/ios_members.cc (static only on 3.0, both on mainline)
Under the assumption that there will be at least one merge from
mainline to the 3.0 branch of libstdc++-v3 before gcc 3.0 is released,
I will focus on mainline problems (in next e-mails).
Regards,
Loren