Errors with Re: [PATCH/RFA] Revamp wctomb/mbtowc conversion, add more charset support

[Corinna Vinschen]

On Mar 26 10:34, Corinna Vinschen wrote:
> On Mar 26 04:29, Hans-Peter Nilsson wrote:
> > > Date: Fri, 20 Mar 2009 13:00:02 +0100
> > > From: Corinna Vinschen <vinschen@redhat.com>
> > 
> > > Part 1 of the patch below, everything except the changes in libc/ctype.
> > 
> > I can't find any mentioning how you tested these patches.  Could
> > you please regtest gcc with all applicable languages on a
> > non-cygwin newlib (simulator) target of your choice?  I'm not
> > ruling out the gcc regressions being visible on cygwin too, I'm
> > just assuming you regtested gcc for cygwin and these changes.
> 
> No, I'm not building gcc, I'm building and testing Cygwin itself.
> 
> > +libstdc++.sum 27_io/basic_ostream/inserters_arithmetic/wchar_t/6.cc
> > 
> > All of them are execution test failures:
> > FAIL: 27_io/basic_ostream/inserters_arithmetic/wchar_t/6.cc execution test
> > 
> > with the message in gfortran.log being:
> >  program stopped with signal 6.
> > which is the result of calling abort; the usual way that gcc
> > test-cases react to inconsistencies, as you know.
> > 
> > For the libstdc++ tests, I see assertion errors like:
> > assertion "err == ios_base::eofbit" failed: file
> > "/tmp/candtestnewlib/gcc/libstdc++-v3/testsuite/22_locale/num_get/get/char/12.cc",
> > line 108, function: void test01()
> > program stopped with signal 6.
> 
> It would be much more helpful if you send a simple testcase to
> demonstrate the problem.  I'm not involved in gcc development.
> It works fine on Cygwin after I fixed a bug in loadlocale yesterday.

I think I found the culprit.  All the failing tests have something to
do with string to numerical conversion, which led me to the fact that
I checked in some files in this area accidentally on the 24th.
I reverted the erroneous checkin now.


Corinna

-- 
Corinna Vinschen
Cygwin Project Co-Leader
Red Hat