https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107608
--- Comment #28 from Xi Ruoyao <xry111 at gcc dot gnu.org> --- (In reply to Jakub Jelinek from comment #27) > For GCC 13, I think it is important that we e.g. don't miscompile glibc > libm, so > the libm testsuite should be clean. PR107967 fixed some of the failures, > and some were claimed to be dups of this PR. So, would be nice to test GCC > with your patch on glibc + libm testsuite. Some bugs are hidden on x86/x86_64 because glibc uses more assembly for FP than oother ports. It's better to try on RISC-V etc. > Just > CC=/path/to/patched-gcc-trunk/gcc CXX=/path/to/patched-gcc-trunk/g++ > ../configure --prefix=/usr > CC=/path/to/patched-gcc-trunk/gcc CXX=/path/to/patched-gcc-trunk/g++ make -jN > CC=/path/to/patched-gcc-trunk/gcc CXX=/path/to/patched-gcc-trunk/g++ make > -jN check > should be enough in latest glibc (and perhaps compare that to GCC 12).
