Changes in chapter08/gcc.xml [670f55f:54eb9b7]

File:

• chapter08/gcc.xml (modified) (7 diffs)

chapter08/gcc.xml

@@ -55 +55 @@
     <screen><userinput remap="pre">patch -Np1 -i ../&gcc-upstream-fixes-patch;</userinput></screen>
 -->
-    <para>If building on x86_64, change the default directory name for 64-bit
-    libraries to <quote>lib</quote>:</para>
-
-<screen><userinput remap="pre">case $(uname -m) in
-  x86_64)
-    sed -e '/m64=/s/lib64/lib/' \
-        -i.orig gcc/config/i386/t-linux64
-  ;;
-esac</userinput></screen>
+    <para>On ARM64 hosts, set the default directory name for
+    64-bit libraries to <quote>lib</quote>:</para>
+
+<screen><userinput remap="pre">sed -e '/lp64=/s/lib64/lib/' \
+    -i.orig gcc/config/aarch64/t-aarch64-linux</userinput></screen>
 
     <para>The GCC documentation recommends building GCC in a dedicated build directory:</para>
@@ -161 +157 @@
     <ulink url="https://gcc.gnu.org/ml/gcc-testresults/"/>.</para>
 
-    <para>In gcc, eleven tests, in the i386 test suite are known to FAIL.
-    It's because the test files do not account for the
+    <para>In gcc tests, the tests related to
+    <filename>fuse_adrp_add_1.c</filename>,
+    <filename>pr63304_1.c</filename>,
+    <filename>pr70120-2.c</filename>,
+    <filename>pr78733.c</filename>,
+    <filename>pr78796.c</filename>,
+    <filename>pr79041-2.c</filename>,
+    <filename>pr94530.c</filename>,
+    <filename>pr94577.c</filename>,
+    <filename>reload-valid-spoff.c</filename>, and
+    many <filename>aapcs64</filename> tests are known to fail.
+    They are because the test files do not account for the
     <parameter>--enable-default-pie</parameter> option.</para>
+
+    <para>In gcc tests, the tests related to
+    <filename>pr104005.c</filename>,
+    <filename>pr103147-10.C</filename>,
+    <filename>shrink_wrap_1.c</filename>,
+    <filename>stack-check-cfa-1.c</filename>,
+    <filename>stack-check-cfa-2.c</filename>,
+    <filename>test_frame_17.c</filename>, and
+    many <filename>sve/pcs</filename> tests are known
+    to fail.  The g++ test related to <filename>pr103147-10.C</filename>
+    is known to fail.  They are because the test files do not account for
+    the <parameter>--enable-default-ssp</parameter> option.</para>
 
     <para>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.</para>
+
+    <!-- Already known via gcc-testresults@gcc.gnu.org -->
+    <para>On ARM64,
+    four g++ tests related to <filename>Waddress-5.C</filename>,
+    twelve g++ tests related to <filename>attrs-10.C</filename>,
+    four g++ tests related to <filename>declare-simd-8.C</filename>,
+    one gcc tests related to <filename>ssa-dom-thread-7.c</filename>,
+    one gcc tests related to <filename>fcsel_1.c</filename>,
+    one gcc tests related to <filename>mgeneral-regs_3.c</filename>, and
+    four gcc tests related to <filename>vqdmlalh_laneq*.c</filename>
+    are known to fail.</para>
+
+    <!-- Need further investigation -->
+    <para>Many gcc and g++ tests related to hwasan are known to fail.
+    And, two tests related to <filename>thread_leak1.c</filename> are known
+    to fail for both gcc and g++.</para>
 
     <para>A few unexpected failures cannot always be avoided. The GCC developers
@@ -224 +258 @@
   platform-specific differences in the dynamic linker name):</para>
 
-<screen><computeroutput>[Requesting program interpreter: /lib64/ld-linux-x86-64.so.2]</computeroutput></screen>
+<screen><computeroutput>[Requesting program interpreter: /lib/ld-linux-aarch64.so.1]</computeroutput></screen>
 
   <para>Now make sure that we're setup to use the correct start files:</para>
@@ -232 +266 @@
   <para>The output of the last command should be:</para>
 
-<screen><computeroutput>/usr/lib/gcc/x86_64-pc-linux-gnu/&gcc-version;/../../../../lib/Scrt1.o succeeded
-/usr/lib/gcc/x86_64-pc-linux-gnu/&gcc-version;/../../../../lib/crti.o succeeded
-/usr/lib/gcc/x86_64-pc-linux-gnu/&gcc-version;/../../../../lib/crtn.o succeeded</computeroutput></screen>
+<screen><computeroutput>/usr/lib/gcc/aarch64-unknown-linux-gnu/&gcc-version;/../../../../lib/Scrt1.o succeeded
+/usr/lib/gcc/aarch64-unknown-linux-gnu/&gcc-version;/../../../../lib/crti.o succeeded
+/usr/lib/gcc/aarch64-unknown-linux-gnu/&gcc-version;/../../../../lib/crtn.o succeeded</computeroutput></screen>
 
   <para>Depending on your machine architecture, the above may differ slightly.
@@ -251 +285 @@
 
 <screen><computeroutput>#include &lt;...&gt; search starts here:
- /usr/lib/gcc/x86_64-pc-linux-gnu/&gcc-version;/include
+ /usr/lib/gcc/aarch64-unknown-linux-gnu/&gcc-version;/include
  /usr/local/include
- /usr/lib/gcc/x86_64-pc-linux-gnu/&gcc-version;/include-fixed
+ /usr/lib/gcc/aarch64-unknown-linux-gnu/&gcc-version;/include-fixed
  /usr/include</computeroutput></screen>
 
@@ -266 +300 @@
   be ignored, but otherwise the output of the last command should be:</para>
 
-<screen><computeroutput>SEARCH_DIR("/usr/x86_64-pc-linux-gnu/lib64")
+<screen><computeroutput>SEARCH_DIR("/usr/aarch64-unknown-linux-gnu/lib64")
 SEARCH_DIR("/usr/local/lib64")
 SEARCH_DIR("/lib64")
 SEARCH_DIR("/usr/lib64")
-SEARCH_DIR("/usr/x86_64-pc-linux-gnu/lib")
+SEARCH_DIR("/usr/aarch64-unknown-linux-gnu/lib")
 SEARCH_DIR("/usr/local/lib")
 SEARCH_DIR("/lib")
@@ -302 +336 @@
   platform-specific differences in dynamic linker name):</para>
 
-<screen><computeroutput>found ld-linux-x86-64.so.2 at /usr/lib/ld-linux-x86-64.so.2</computeroutput></screen>
+<screen><computeroutput>found ld-linux-aarch64.so.1 at /usr/lib/ld-linux-aarch64.so.1</computeroutput></screen>
 
   <para>If the output does not appear as shown above or is not received