Changes in chapter08/gcc.xml [09f2a24:5f2ba8c]

File:

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

chapter08/gcc.xml

@@ -55 +55 @@
     <screen><userinput remap="pre">patch -Np1 -i ../&gcc-upstream-fixes-patch;</userinput></screen>
 -->
-
-    <!-- https://gcc.gnu.org/r14-4674 -->
-    <para>Again, fix an issue producing illegal instructions in linked
-    executables and shared libraries with GCC &gcc-version; and
-    Binutils-2.42:</para>
-
-    <screen><userinput remap='pre'>sed -e '/ASM_OUTPUT_ALIGN_WITH_NOP/,+1d' \
-    -i gcc/config/loongarch/loongarch.h</userinput></screen>
-
-    <para>Set the default directory name for
-    64-bit libraries to <quote>lib</quote>:</para>
-
-<screen><userinput remap="pre">sed -e 's/lib64/lib/' \
-    -i.orig gcc/config/loongarch/{t-linux,linux.h}</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>The GCC documentation recommends building GCC in a dedicated build directory:</para>
@@ -179 +174 @@
 
     <para>
-    Twelve gcc tests (out of over 150,000):
-    seven tests in the <filename class='directory'>analyzer</filename>
-    directory, one test named <filename>gcc.dg/uninit-pred-9_b.c</filename>,
-    one test named <filename>pr108357.c</filename>, one test named
-    <filename>ssa-dom-cse-2.c</filename>, and two
-    <quote>stack-check-cfa-*.c</quote> tests are known to fail.
-
-    For g++, 23 tests (out of approximately 250,000): 14
+    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.
+
+    For g++, 21 tests (out of approximately 250,000): 14
     <quote>AddressSanitizer*</quote>
-    tests, 7 <filename>interception-malloc-test-1.C</filename> tests,
-    one <filename>pr90883.C</filename> test, and one
-    <filename>pr64076</filename> test are known to fail.
-    </para>
+    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. The GCC developers
@@ -241 +240 @@
   platform-specific differences in the dynamic linker name):</para>
 
-<screen><computeroutput>[Requesting program interpreter: /lib64/ld-linux-loongarch-lp64d.so.1]</computeroutput></screen>
+<screen><computeroutput>[Requesting program interpreter: /lib64/ld-linux-x86-64.so.2]</computeroutput></screen>
 
   <para>Now make sure that we're set up to use the correct start files:</para>
@@ -249 +248 @@
   <para>The output of the last command should be:</para>
 
-<screen><computeroutput>/usr/lib/gcc/loongarch64-unknown-linux-gnu/&gcc-version;/../../../../lib/Scrt1.o succeeded
-/usr/lib/gcc/loongarch64-unknown-linux-gnu/&gcc-version;/../../../../lib/crti.o succeeded
-/usr/lib/gcc/loongarch64-unknown-linux-gnu/&gcc-version;/../../../../lib/crtn.o succeeded</computeroutput></screen>
+<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>
 
   <para>Depending on your machine architecture, the above may differ slightly.
@@ -268 +267 @@
 
 <screen><computeroutput>#include &lt;...&gt; search starts here:
- /usr/lib/gcc/loongarch64-unknown-linux-gnu/&gcc-version;/include
+ /usr/lib/gcc/x86_64-pc-linux-gnu/&gcc-version;/include
  /usr/local/include
- /usr/lib/gcc/loongarch64-unknown-linux-gnu/&gcc-version;/include-fixed
+ /usr/lib/gcc/x86_64-pc-linux-gnu/&gcc-version;/include-fixed
  /usr/include</computeroutput></screen>
 
@@ -283 +282 @@
   be ignored, but otherwise the output of the last command should be:</para>
 
-<screen><computeroutput>SEARCH_DIR("/usr/loongarch64-unknown-linux-gnu/lib64")
+<screen><computeroutput>SEARCH_DIR("/usr/x86_64-pc-linux-gnu/lib64")
 SEARCH_DIR("/usr/local/lib64")
 SEARCH_DIR("/lib64")
 SEARCH_DIR("/usr/lib64")
-SEARCH_DIR("/usr/loongarch64-unknown-linux-gnu/lib")
+SEARCH_DIR("/usr/x86_64-pc-linux-gnu/lib")
 SEARCH_DIR("/usr/local/lib")
 SEARCH_DIR("/lib")
 SEARCH_DIR("/usr/lib");</computeroutput></screen>
-<!--
+
    <para>A 32-bit system may use a few other directories. For example, here
    is the output from an i686 machine:</para>
@@ -303 +302 @@
 SEARCH_DIR("/lib")
 SEARCH_DIR("/usr/lib");</computeroutput></screen>
--->
+
   <para>Next make sure that we're using the correct libc:</para>
 
@@ -319 +318 @@
   platform-specific differences in dynamic linker name):</para>
 
-<screen><computeroutput>found ld-linux-loongarch-lp64d.so.1 at /usr/lib/ld-linux-loongarch-lp64d.so.1</computeroutput></screen>
+<screen><computeroutput>found ld-linux-x86-64.so.2 at /usr/lib/ld-linux-x86-64.so.2</computeroutput></screen>
 
   <para>If the output does not appear as shown above or is not received