This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Is PR21674 really fixed for gcc 4.2?
- From: Benjamin Kosnik <bkoz at redhat dot com>
- To: howarth at bromo dot msbb dot uc dot edu (Jack Howarth)
- Cc: gcc at gcc dot gnu dot org
- Date: Mon, 18 Sep 2006 10:08:56 +0200
- Subject: Re: Is PR21674 really fixed for gcc 4.2?
- References: <20060916010718.963E9110011@bromo.msbb.uc.edu>
> XPASS: 21_strings/basic_string/element_access/char/21674.cc execution test
> XPASS: 21_strings/basic_string/element_access/wchar_t/21674.cc execution test
>
> in the libstdc++ testsuite. From what I see in bugzilla for PR21674, it
> seems that it should be fixed on gcc trunk, right? Shouldn't the xfail
> line be dropped now from those two test cases for the gcc 4.2 release?
It is expected that these tests fail.
Ie:
%COMP.sh "-g -O0 -D_GLIBCXX_DEBUG" 21_strings/basic_string/element_access/char/21674.cc
%./a.out
/mnt/share/bld/gcc/i686-pc-linux-gnu/libstdc++-v3/include/bits/basic_string.h:709: typename _Alloc::rebind<_CharT>::other::reference std::basic_string<_CharT, _Traits, _Alloc>::operator[](typename _Alloc::rebind<_CharT>::other::size_type) [with _CharT = char, _Traits = std::char_traits<char>, _Alloc = std::allocator<char>]: Assertion '__pos <= size()' failed.
Abort
Thus, the xfail marking.
If this is not asserting on darwin, then something is wrong and this particular test is failing.
-benjamin