https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81797
--- Comment #10 from Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> --- (In reply to Jack Howarth from comment #9) No, I can reproduce this with a build outside Homebrew/ruby. From the command line: $ ../gcc-7.1.0/configure --build=x86_64-apple-darwin17.0.0 --prefix=/usr/local/Cellar/gcc/7.1.0 --with-gmp=/usr/local/opt/gmp --with-mpfr=/usr/local/opt/mpfr --with-mpc=/usr/local/opt/libmpc --with-isl=/usr/local/opt/isl --enable-checking=release --with-native-system-header-dir=/usr/include --with-sysroot=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.13.sdk $ make -j4 The only thing I can think of is that maybe, just maybe, it's due to filesystem timestamp granularity? My 10.13 system is running on APFS filesystem, which has 1 ns granularity (smaller than 1 s for HFS+).
