gronod/lfs
1
0
Fork 0
mirror of https://git.linuxfromscratch.org/lfs.git synced 2025-06-18 19:29:21 +01:00
Code Issues Packages Projects Releases Wiki Activity

gcc: Document tsan failures with some host distros

Browse Source
This commit is contained in:
Xi Ruoyao 2025-02-19 23:19:32 +08:00
parent 5616cb8ee9
commit 6f76f192b9
No known key found for this signature in database
GPG Key ID: ACAAD20E19E710E3
1 changed files with 7 additions and 18 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
chapter08/gcc.xml
View File

@ -173,26 +173,15 @@ su tester -c "PATH=$PATH make -k check"</userinput></screen>
<para>Results can be compared with those located at <ulink <para>Results can be compared with those located at <ulink
url="&test-results;"/> and url="&test-results;"/> and
<ulink url="https://gcc.gnu.org/ml/gcc-testresults/"/>.</para> <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 - -> <!-- https://github.com/google/sanitizers/issues/1716
One libstdc++ test (out of over 15000), <filename>copy.cc</filename>, is Affecting any host distro with a large vm.mmap_rnd_bits.
known to fail. 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>
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>
-->
<para>A few unexpected failures cannot always be avoided. In some cases <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 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.--> are usually aware of these issues, but have not resolved them yet.-->