https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80837
--- Comment #6 from Peter Cordes <peter at cordes dot ca> --- (In reply to Jakub Jelinek from comment #4) > But have just tried gcc 7.1.0 release and can't reproduce even there. Matt says the Compiler Explorer backend uses upstream release tarballs like `URL=ftp://ftp.gnu.org/gnu/gcc/gcc-${VERSION}/${TARBALL}`. (where TARBALL is `gcc-${VERSION}.tar.xz` for recent gcc where .xz is available). The compiler config used is https://github.com/mattgodbolt/compiler-explorer-image/blob/master/gcc/build/build.sh#L78: CONFIG="" CONFIG+=" --build=x86_64-linux-gnu" CONFIG+=" --host=x86_64-linux-gnu" CONFIG+=" --target=x86_64-linux-gnu" CONFIG+=" --disable-bootstrap" CONFIG+=" --enable-multiarch" CONFIG+=" --with-abi=m64" CONFIG+=" --with-multilib-list=m32,m64,mx32" CONFIG+=" --enable-multilib" CONFIG+=" --enable-clocale=gnu" CONFIG+=" --enable-languages=c,c++,fortran" # used to have go, but is incompatible with m32/mx32 CONFIG+=" --enable-ld=yes" CONFIG+=" --enable-gold=yes" CONFIG+=" --enable-libstdcxx-debug" CONFIG+=" --enable-libstdcxx-time=yes" CONFIG+=" --enable-linker-build-id" CONFIG+=" --enable-lto" CONFIG+=" --enable-plugins" CONFIG+=" --enable-threads=posix" CONFIG+=" --with-pkgversion=GCC-Explorer-Build" BINUTILS_VERSION=2.29.1 Does that help figure out how to build a gcc7.1.0 that can repro this?
