On Tue, Nov 8, 2016 at 9:11 AM, Christophe Lyon <christophe.l...@linaro.org> wrote: > Hi, > > On 7 November 2016 at 23:56, Jonathan Wakely <jwakely....@gmail.com> wrote: >> On 7 November 2016 at 22:49, Jason Merrill wrote: >>> Tested x86_64-pc-linux-gnu. Are the libstdc++ changes OK for trunk? >> >> Yes, I like the approach, thanks. > > The new test "g++.dg/cpp1z/noexcept-type11.C" fails on arm: > /aci-gcc-fsf/sources/gcc-fsf/gccsrc/gcc/testsuite/g++.dg/cpp1z/noexcept-type11.C:3:6: > warning: mangled name for 'void f(int (*)() noexcept)' will change in > C++17 because the exception specification is part of a function type > [-Wc++1z-compat] > In function 'void f(int (*)() noexcept)': > cc1plus: warning: mangled name for '<built-in>' will change in C++17 > because the exception specification is part of a function type > [-Wc++1z-compat] > cc1plus: warning: mangled name for '<built-in>' will change in C++17 > because the exception specification is part of a function type > [-Wc++1z-compat] > > FAIL: g++.dg/cpp1z/noexcept-type11.C (test for excess errors) I can confirm this and created PR78269 for tracking. I also noticed noexcept-type9.C fails on both arm/aarch64 target.
Thanks, bin > > > Christophe
