This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: Results for 8.0.1 20180316 (experimental) [trunk revision 258610] (GCC) libstdc++ testsuite on x86_64-pc-linux-gnu
- From: Jonathan Wakely <jwakely dot gcc at gmail dot com>
- To: "libstdc++" <libstdc++ at gcc dot gnu dot org>
- Date: Tue, 20 Mar 2018 18:20:16 +0000
- Subject: Re: Results for 8.0.1 20180316 (experimental) [trunk revision 258610] (GCC) libstdc++ testsuite on x86_64-pc-linux-gnu
- References: <5aacd955.W97SAA9Qc1hoHlKB%jwakely.gcc@gmail.com>
On 17 March 2018 at 09:01, Jonathan Wakely wrote:
> Native configuration is x86_64-pc-linux-gnu
>
> === libstdc++ tests ===
>
>
> Running target unix/-std=gnu++11/-D_GLIBCXX_ASSERTIONS
>
> === libstdc++ Summary for unix/-std=gnu++11/-D_GLIBCXX_ASSERTIONS ===
>
> # of expected passes 12330
> # of expected failures 71
> # of unsupported tests 579
>
> Running target unix/-std=gnu++11/-D_GLIBCXX_DEBUG
> XPASS: 21_strings/basic_string_view/element_access/char/2.cc execution test
> XPASS: 21_strings/basic_string_view/element_access/wchar_t/2.cc execution test
> FAIL: 23_containers/bitset/hash/1.cc (test for excess errors)
> UNRESOLVED: 23_containers/bitset/hash/1.cc compilation failed to produce executable
These debug mode failures are regressions, reported as
https://gcc.gnu.org/PR84998
I think they all have the same root cause (Nathan fixed a bug in G++).