diff --git a/chapter08/gcc.xml b/chapter08/gcc.xml
index b3397d8be..f0616e2cd 100644
--- a/chapter08/gcc.xml
+++ b/chapter08/gcc.xml
@@ -173,26 +173,15 @@ su tester -c "PATH=$PATH make -k check"</userinput></screen>
     <para>Results can be compared with those located at <ulink
     url="&test-results;"/> and
     <ulink url="https://gcc.gnu.org/ml/gcc-testresults/"/>.</para>
-<!--
-    <para>
-    Eight gcc tests (out of over 185,000):
-    <!- - https://gcc.gnu.org/PR106375 - -><filename>pr56837.c</filename>
-    and seven tests in the <filename class='directory'>analyzer</filename>
-    directory are known to fail.
 
-    <!- - https://gcc.gnu.org/PR109353 - ->
-    One libstdc++ test (out of over 15000), <filename>copy.cc</filename>, is
-    known to fail.
+    <!-- https://github.com/google/sanitizers/issues/1716
+         Affecting any host distro with a large vm.mmap_rnd_bits.
+         The fix is https://github.com/llvm/llvm-project/commit/0784b1eefa36
+         but it's not in GCC 14.  TODO retry with
+             sudo sysctl vm.mmap_rnd_bits=32
+         on the host distro when we update to GCC 15.  -->
+    <para>The tsan tests are known to fail on some host distros.</para>
 
-    For g++, 21 tests (out of approximately 250,000): 14
-    <quote>AddressSanitizer*</quote>
-    tests and 7 <filename>interception-malloc-test-1.C</filename> tests, are
-    known to fail.
-
-    Additionally, several tests in the
-    <filename class='directory'>vect</filename> directory are known to fail
-    if the hardware does not support AVX.</para>
--->
     <para>A few unexpected failures cannot always be avoided. In some cases
     test failures depend on the specific hardware of the system.<!--The GCC developers
     are usually aware of these issues, but have not resolved them yet.-->