https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103907
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
I just did:
make check-g++ RUNTESTFLAGS="dg.exp=*array*.C --target_board=unix/-m32" and
got:
=== g++ tests ===
Schedule of variations:
unix/-m32
Running target unix/-m32
Using /usr/share/dejagnu/baseboards/unix.exp as board description file for
target.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
Using /home/apinski/src/upstream-gcc/gcc/gcc/testsuite/config/default.exp as
tool-and-target-specific interface file.
Running /home/apinski/src/upstream-gcc/gcc/gcc/testsuite/g++.dg/dg.exp ...
FAIL: g++.dg/eh/array2.C -std=c++98 execution test
FAIL: g++.dg/eh/array2.C -std=c++14 execution test
FAIL: g++.dg/eh/array2.C -std=c++17 execution test
FAIL: g++.dg/eh/array2.C -std=c++2a execution test
=== g++ Summary ===
# of expected passes 2807
# of unexpected failures 4
# of expected failures 60
# of unsupported tests 146
I have not looked into why g++.dg/eh/array2.C fails though.
This is why I asked if you forgot to rebuild the 32bit multilib libstdc++.
