Changeset 0238d49 for chapter06/gcc.xml

Timestamp:

04/24/2015 09:19:59 PM (9 years ago)

Author:

Bruce Dubbs <bdubbs@…>

Branches:

10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc

Children:

74c099b

Parents:

320fdc6

Message:

Update known regression test failures for gcc and glibc.

git-svn-id: ​http://svn.linuxfromscratch.org/LFS/trunk/BOOK@10906 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

File:

• chapter06/gcc.xml (modified) (2 diffs)

chapter06/gcc.xml

@@ -41 +41 @@
   <sect2 role="installation">
     <title>Installation of GCC</title>
-<!--
-    <para>As in Chapter 5, fix a problem identified upstream:</para>
-
-<screen><userinput remap="pre">sed -i 's/if \((code.*))\)/if (\1 \&amp;\&amp; \!DEBUG_INSN_P (insn))/' gcc/sched-deps.c</userinput></screen>
-
-
-    <para>Now fix another problem identified upstream that causes some 
-    programs to fail:</para>
-
-<screen><userinput remap="pre">patch -Np1 -i ../&gcc-upstream-patch;</userinput></screen>
--->
+
     <para>The GCC documentation recommends building GCC outside of the source
     directory in a dedicated build directory:</para>
@@ -122 +112 @@
 
     <para>A few unexpected failures cannot always be avoided. The GCC developers
-    are usually aware of these issues, but have not resolved them yet. <!-- In
-    particular, the <filename class="libraryfile">libmudflap</filename> tests
-    are known to be particularly problematic as a result of a bug in GCC
-    (<ulink url="http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20003"/>). -->
+    are usually aware of these issues, but have not resolved them yet.
+    In particular, four tests in the libgomp test suite are known to fail.
     Unless the test results are vastly different from those at the above URL,
     it is safe to continue.</para>