https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96734
--- Comment #6 from Ariadne Conill <ariadne at dereferenced dot org> --- (In reply to Ariadne Conill from comment #5) > I should clarify. > > I cross-compiled g++ 10.2.0 to run on mips64 *host*. That part worked fine. > > Afterwards, the *host* mips64 g++ cannot compile itself. > > The *host* mips64 g++ (which was cross-compiled from an aarch64 machine), is > built with: > > Configured with: /home/buildozer/aports/main/gcc/src/gcc-10.2.0/configure > --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info > --build=mips64-alpine-linux-musl --host=mips64-alpine-linux-musl > --target=mips64-alpine-linux-musl --with-pkgversion='Alpine 10.2.0' > --enable-checking=release --disable-fixed-point --disable-libstdcxx-pch > --disable-multilib --disable-nls --disable-werror --disable-symvers > --enable-__cxa_atexit --enable-default-pie --enable-default-ssp > --enable-cloog-backend --enable-languages=c,c++,d,objc,fortran,ada > --with-arch=mips3 --with-tune=mips64 --with-mips-plt --with-float=soft > --with-abi=64 --disable-bootstrap --disable-libquadmath --disable-libssp > --disable-libmpx --disable-libmudflap --disable-libsanitizer --enable-shared > --enable-threads --enable-tls --disable-libitm --with-system-zlib > --with-linker-hash-style=sysv > > So we have this crashing whenever we try to build gcc with 10.2.0 on a > mips64 host, either rebuilding from gcc 9.3.0 or from cross-compiled 10.2.0. An easy way to observe the behavior for yourself would be to use an Alpine chroot on a mips64 host (I think the GCC build farm has one, if not, I can facilitate access to a mips64 container).
