[lfs] 02/02: gcc: update known failures and add the change log entry

"Git Owner" ([email protected] via lfs-book Mailing List) <[email protected]>
Newsgroups gmane.linux.lfs.book
Message-ID <[email protected]>
This is an automated email from the git hooks/post-receive script.

git pushed a commit to branch trunk
in repository lfs.

commit 1be59656419d06423421b8f8e2f4b75e3f0b7401
Author: Xi Ruoyao <[email protected]>
AuthorDate: Mon May 11 23:10:54 2026 +0800

    gcc: update known failures and add the change log entry
---
 chapter01/changelog.xml | 10 ++++++++++
 chapter08/gcc.xml       | 51 +++++++++++++++++++++++++++++--------------------
 2 files changed, 40 insertions(+), 21 deletions(-)

diff --git a/chapter01/changelog.xml b/chapter01/changelog.xml
index a663a8877..f332e0ec2 100644
--- a/chapter01/changelog.xml
+++ b/chapter01/changelog.xml
@@ -40,6 +40,16 @@
     appropriate for the entry or if needed the entire day's listitem.
     -->
 
+    <listitem>
+      <para>2026-05-08</para>
+      <itemizedlist>
+        <listitem>
+          <para>[bdubbs] - Update to gcc-16.1.0.  Fixes
+          <ulink url='&lfs-ticket-root;5927'>#5927</ulink>.</para>
+        </listitem>
+      </itemizedlist>
+    </listitem>
+
     <listitem>
       <para>2026-05-01</para>
       <itemizedlist>
diff --git a/chapter08/gcc.xml b/chapter08/gcc.xml
index 884652ac1..52e5978c7 100644
--- a/chapter08/gcc.xml
+++ b/chapter08/gcc.xml
@@ -191,10 +191,6 @@ cd       build</userinput></screen>
 
 <screen><userinput remap="test">ulimit -s -H unlimited</userinput></screen>
 
-    <para>Now remove several known test failures:</para>
-
-<screen><userinput remap="test">sed -e '/cpython/d' -i ../gcc/testsuite/gcc.dg/plugin/plugin.exp</userinput></screen>
-
     <para>Test the results as a non-privileged user, but do not stop at errors:</para>
 
 <screen><userinput remap="test">chown -R tester .
@@ -211,23 +207,36 @@ su tester -c "PATH=$PATH make -k check"</userinput></screen>
     url="&test-results;"/> and
     <ulink url="https://gcc.gnu.org/ml/gcc-testresults/"/>.</para>
 
-    <!-- https://gcc.gnu.org/PR118885 -->
-    <para>Four tests related to <filename>pr90579.c</filename> are known
-    to fail.</para>
-
-    <!-- https://gcc.gnu.org/PR124682 -->
-    <para>Eight tests related to <filename>builtin-math-6.c</filename> are
-    known to fail.</para>
-
-    <para>Five tests related to <filename>analyzer/strchr-1.c</filename> are known
-    to fail.</para>
-
-    <!-- https://gcc.gnu.org/pipermail/gcc-patches/2026-February/708384.html -->
-    <para>Four tests in libstdc++, <filename>17_intro/badnames.cc</filename>,
-    <filename>17_intro/names.cc</filename>,
-    <filename>17_intro/names_fortify.cc</filename>, and
-    <filename>experimental/names.cc</filename>, are known to fail due to changes
-    with glibc-2.43.</para>
+    <para>In the <filename class='directory'>gcc.target/i386</filename>
+    tests, the tests named
+    <filename>auto-init-padding-9.c</filename>,
+    <filename>builtin-memmove-*.c</filename>,
+    <filename>mem{cpy,set}-pr120683-*.c</filename>,
+    <filename>pr111657-1.c</filename>,
+    <filename>pr115102.c</filename>,
+    <filename>pr116896.c</filename>,
+    <filename>pr120881-2a.c</filename>, and
+    <filename>pr122343-4a.c</filename> are known to fail.
+    The test named <filename>shift-gf2p8affine-2.c</filename> is known
+    to fail if the processor does not support AVX512.</para>
+
+    <para>In the <filename class='directory'>g++.target/i386</filename>
+    tests, the tests named
+    <filename>memset-pr108585-1{a,b}.C</filename>,
+    <filename>mv{,c}-symbols*.C</filename>,
+    <filename>pr112824-2.C</filename>, and
+    <filename>pr116896-1.C</filename> are known to fail.</para>
+
+    <para>Additionally, the tests
+    <filename>gcc.dg/ipa/pr122458.c</filename>,
+    <filename>gcc.dg/lto/toplevel-*-asm-*</filename>, and
+    <filename>gcc.dg/plugin/crash-test-nested-*.c</filename> are known to
+    fail.</para>
+
+    <para>The LFS editors have investigated those failures and confirmed
+    none indicates a critical issue.  Most of them are because the test case
+    author did not anticipate <parameter>--enable-default-ssp</parameter> or
+    <parameter>--enable-default-pie</parameter>.</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

-- 
To stop receiving notification emails like this one, please contact
the administrator of this repository.

-- 
http://lists.linuxfromscratch.org/sympa/info/lfs-book
Unsubscribe: See the above information page
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.