Status of 9.0.0 20190110 (experimental) [trunk revision 267818] (GCC) testsuite on x86_64-w64-mingw32

[Jonathan Wakely]

On Wed, 16 Jan 2019 at 11:12, Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
>
> On Fri, 11 Jan 2019 at 10:16, Rainer Emrich wrote:
> >
> > There was a bug which prevented building libgfortran. Now after the
> > issue is fixed, see https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88331,
> > I have posted new testresults.
> >
> > https://gcc.gnu.org/ml/gcc-testresults/2019-01/msg01052.html
> >
> > Compared to rev. 265163 we have the following changes:
> >
> > acats tests:
> > 15 new unexpected failures
> >
> > g++ tests:
> > 155 additional unexpected failures
> >
> > gcc tests:
> > 63 additional unexpected failures
> >
> > gfortran tests:
> > 22 additional unexpected failures
> >
> > gnat tests:
> > 1 additional unexpected successes
> >
> > obj-c++ tests:
> > 5 additional unexpected failures
> >
> > objc tests:
> > no difference
> >
> > libatomic:
> > no difference
> >
> > libgomp:
> > 71 additional unexpected failures
> >
> > libstdc++ tests:
> > 5 additional unexpected failures
> >
> > You may find the complete logs at
> > https://cloud.emrich-ebersheim.de/index.php/s/g9D245XdCW6GD5W
> >
> > I hope this helps.
> >
> > Rainer
>
>
> Thanks for this!
>
> Most of the libstdc++ failures are expected (and I can fix most of the
> std::filesystem ones) but I'm confused by two of them that fail to
> link:
[...]

Also by this one:

terminate called after throwing an instance of
'std::filesystem::__cxx11::filesystem_error'
  what():  filesystem error: cannot create symlink [.]
[filesystem-test.0.15180-read_symlink]
FAIL: 27_io/filesystem/operations/read_symlink.cc execution test

The test has:

// { dg-xfail-if "symlinks not supported" { *-*-mingw* } }

So is expected to fail on this target.