[Bug libstdc++/61532] New: [4.10 regression] make_signed and make_unsigned wchar_t have started failing in the libstdc++ testsuite.

[ramana at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61532

            Bug ID: 61532
           Summary: [4.10 regression]  make_signed and make_unsigned
                    wchar_t have started failing in the libstdc++
                    testsuite.
           Product: gcc
           Version: 4.10.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: ramana at gcc dot gnu.org

Somewhere between 210455 and 210475 these tests started failing on
arm-none-linux-gnueabihf. I see the same failures on aarch64-none-elf too.


FAIL: 20_util/make_signed/requirements/typedefs-1.cc (test for excess errors)
FAIL: 20_util/make_signed/requirements/typedefs-2.cc (test for excess errors)
FAIL: 20_util/make_unsigned/requirements/typedefs-1.cc (test for excess errors)
FAIL: 20_util/make_unsigned/requirements/typedefs-2.cc (test for excess errors)
FAIL: tr1/2_general_utilities/shared_ptr/modifiers/reset_neg.cc  (test for
errors, line 36)

All with 

   static_assert( is_same<test23_type, volatile signed wchar_t>::value,


or their equivalent.

In C on ARM the wchar_t type is defined to unsigned int on AAPCS configurations
which is true for Linux, I'm not sure what we do in C++ but I expect this to be
the same. I suspect there is something underlying here for all targets that
define wchar_t to be unsigned int by default.

Looking at other testresults in June it looks like atleast the first 2 tests
fail on powerpc-linux and powerpc-aix 




regards
Ramana