[lfs] 03/04: arm64: update gcc known failures

"Git Owner" ([email protected] via lfs-book Mailing List) <[email protected]> Mon, 25 May 2026 17:11:05 +0000
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 xry111/arm64
in repository lfs.

commit f0a05c003b107383ad4ff187710542d8f1c70acf
Author: Xi Ruoyao <[email protected]>
AuthorDate: Fri May 22 14:10:21 2026 +0800

    arm64: update gcc known failures
---
 chapter08/gcc.xml | 33 ++++++++++++++++++++++-----------
 1 file changed, 22 insertions(+), 11 deletions(-)

diff --git a/chapter08/gcc.xml b/chapter08/gcc.xml
index aa0912afa..dd8d763f7 100644
--- a/chapter08/gcc.xml
+++ b/chapter08/gcc.xml
@@ -194,15 +194,26 @@ su tester -c "PATH=$PATH make -k check"</userinput></screen>
     url="&test-results;"/> and
     <ulink url="https://gcc.gnu.org/ml/gcc-testresults/"/>.</para>
 
-    <!-- TODO: why?? -->
+    <!-- predcom-8.c: PR118407
+         atomic_store_with_stshh.{c,C}: need -fno-stack-protector
+         mv-*: PR125126
+         TODO: others why?? -->
     <para>On ARM64, many tests in
-    the <filename class='directory'>c-c++-common/hwasan</filename>
-    directory are known to fail.
-    The tests named <filename>locally_streaming_1.c</filename>,
+    the <filename class='directory'>c-c++-common/hwasan</filename>,
+    the <filename class='directory'>gcc.target/aarch64/pch</filename>,
+    and the <filename class='directory'>gcc.target/aarch64/memtag</filename>
+    directories are known to fail.
+    The tests named <filename>atomic_store_with_stshh.{c,C}</filename>,
+    <filename>locally_streaming_1{,_nosve}.c</filename>,
     <filename>memset-strict-align-1.c</filename>,
-    <filename>nonlocal_goto_*.c</filename>,
-    <filename>pr113618.c</filename>, and
-    <filename>pr114991.c</filename> are also known to fail.</para>
+    <filename>mv-and-mvc3.{c,C}</filename>,
+    <filename>mv-symbols*.{c,C}</filename>,
+    <filename>nonlocal_goto_{1,3}.c</filename>,
+    <filename>pr113618.c</filename>,
+    <filename>pr114991.c</filename>, and
+    <filename>predcom-8.c</filename> are also known to fail.
+    The tests named <filename>pr122475.c</filename> are known to fail
+    if the CPU does not support SVE.</para>
 
     <para>Additionally, the tests
     <filename>gcc.dg/ipa/pr122458.c</filename>,
@@ -210,12 +221,12 @@ su tester -c "PATH=$PATH make -k check"</userinput></screen>
     <filename>gcc.dg/plugin/crash-test-nested-*.c</filename> are known to
     fail.  The test <filename>g++.dg/gomp/deprecate-1.C</filename> is known
     to fail sometimes.</para>
-
+<!-- I've not really tried hard analyzing gcc failures on aarch64
     <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>
-
+    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
     are usually aware of these issues, but have not resolved them yet.-->

-- 
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