diff --git a/chapter08/gcc.xml b/chapter08/gcc.xml
index 52640ce39..767e0aebf 100644
--- a/chapter08/gcc.xml
+++ b/chapter08/gcc.xml
@@ -156,10 +156,32 @@ su tester -c "PATH=$PATH make -k check"
url="&test-results;"/> and
.
- In gcc, eleven tests, in the i386 test suite are known to FAIL.
- It's because the test files do not account for the
+ In gcc tests, the tests related to
+ fuse_adrp_add_1.c,
+ pr63304_1.c,
+ pr70120-2.c,
+ pr78733.c,
+ pr78796.c,
+ pr79041-2.c,
+ pr94530.c,
+ pr94577.c,
+ reload-valid-spoff.c, and
+ many aapcs64 tests are known to fail.
+ They are because the test files do not account for the
--enable-default-pie option.
+ In gcc tests, the tests related to
+ pr104005.c,
+ pr103147-10.C,
+ shrink_wrap_1.c,
+ stack-check-cfa-1.c,
+ stack-check-cfa-2.c,
+ test_frame_17.c, and
+ many sve/pcs tests are known
+ to fail. The g++ test related to pr103147-10.C
+ is known to fail. They are because the test files do not account for
+ the --enable-default-ssp option.
+
In g++, four tests related to PR100400 are known to be reported
as both XPASS and FAIL. It's because the test file for this known issue
is not well written.
@@ -176,7 +198,9 @@ su tester -c "PATH=$PATH make -k check"
are known to fail.
- Many gcc and g++ tests related to hwasan are known to fail.
+ Many gcc and g++ tests related to hwasan are known to fail.
+ And, two tests related to thread_leak1.c are known
+ to fail for both gcc and g++.
A few unexpected failures cannot always be avoided. The GCC developers
are usually aware of these issues, but have not resolved them yet.