https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #82 from dave.anglin at bell dot net --- On 2019-07-23 11:06 a.m., elowe at elowe dot com wrote: > During stage0 - MPFR will ICE in GCC4.9.3 due to TLS. You need to go into the > MPFR directory and re-run the same configure line from config.log, but add > --disable-thread-safe. Can't you add --disable-thread-safe to configure options for gcc build? I think it will get passed to MPFR. I usually build gmp, mpfr and mpc separately from gcc and install them where gcc infrastructure can find them. > > The stage1 compiler will now build. Woot managed to build some version of gcc > 8.3 > > During stage1 - MPFR will ICE in the stage1 xgcc also due to TLS. Again you > need to --disable-thread-safe for MPFR (making sure to set CC correctly) > > The stage2 compiler will now build - hey it managed to build itself. > > The stage2 compiler will ICE while building > ../../../../gcc-8.3.0/libstdc++-v3/libsupc++/array_type_info.cc > > well that was unexpected, since it did build itself once, but it failed > apparently while building stage3. Unfortunately, this indicates that the stage2 compiler is broken (miscompiled by stage1). One could compare the .s files generated by the stage1 and stage2 compilers. We need details of ICE and preprocessed source for array_type_info.cc. A regression search to find which change introduced this bug would also be very helpful.
