[lfs] 01/04: Merge remote-tracking branch 'origin/trunk' into xry111/arm64

"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 xry111/arm64
in repository lfs.

commit d2ba2d38b245addda9b697f07a938601dbbd47a7
Merge: 20ef16e4f 514c9e71b
Author: Xi Ruoyao <[email protected]>
AuthorDate: Thu Feb 27 19:31:35 2025 +0800

    Merge remote-tracking branch 'origin/trunk' into xry111/arm64

 appendices/dependencies.xml |  2 +-
 chapter01/changelog.xml     | 14 ++++++++++++++
 chapter08/bison.xml         |  2 +-
 chapter08/e2fsprogs.xml     |  7 +++++--
 chapter08/flex.xml          |  2 +-
 chapter08/gcc.xml           | 26 +++++++-------------------
 chapter08/gettext.xml       |  3 +--
 chapter08/libtool.xml       |  2 +-
 chapter08/man-pages.xml     | 27 ++++++++++++++++++++++++++-
 chapter08/perl.xml          |  2 +-
 chapter08/systemd.xml       |  6 +++++-
 gen-changelog.py            |  2 +-
 packages.ent                | 12 ++++++------
 13 files changed, 70 insertions(+), 37 deletions(-)

diff --cc chapter08/gcc.xml
index 937d2d4ac,f0616e2cd..5f7e9636b
--- a/chapter08/gcc.xml
+++ b/chapter08/gcc.xml
@@@ -165,43 -173,15 +165,31 @@@ su tester -c "PATH=$PATH make -k check"
      <para>Results can be compared with those located at <ulink
      url="&test-results;"/> and
      <ulink url="https://gcc.gnu.org/ml/gcc-testresults/"/>.</para>
- <!--
-     <para>
-     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 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>
- -->
+ 
+     <!-- https://github.com/google/sanitizers/issues/1716
+          Affecting any host distro with a large vm.mmap_rnd_bits.
+          The fix is https://github.com/llvm/llvm-project/commit/0784b1eefa36
+          but it's not in GCC 14.  TODO retry with
+              sudo sysctl vm.mmap_rnd_bits=32
+          on the host distro when we update to GCC 15.  -->
+     <para>The tsan tests are known to fail on some host distros.</para>
  
 +    <!-- https://gcc.gnu.org/PR111224 for modules.
 +         https://gcc.gnu.org/PR112376 for ssa-dom-thread-7.
 +         TODO: for others why?? -->
 +    <para>On ARM64, many tests in
 +    the <filename class='directory'>c-c++-common/hwasan</filename>,
 +    the <filename class='directory'>gcc.target/aarch64/sve/acle</filename>
 +    directory,
 +    the <filename class='directory'>gcc.target/aarch64/sme</filename>
 +    directory,
 +    and the
 +    <filename class='directory'>g++.dg/modules</filename>
 +    directory are known to fail.
 +    The tests named <filename>memset-strict-align-1.c</filename>,
 +    <filename>ssa-dom-thread-7.c</filename>, and
 +    <filename>pr113618.c</filename> are also known to fail.</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
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.