mirror of
https://git.linuxfromscratch.org/lfs.git
synced 2025-07-22 20:25:04 +01:00
gcc: Decorate test failures, remove outdated comments, ...
move comments for upstream PR links to correct location. BTW data-model-4.c is also in analyzer directory, so we can just say 7 analyzer tests.
This commit is contained in:
parent
0800455fb6
commit
5f2ba8ce99
@ -172,48 +172,30 @@ su tester -c "PATH=$PATH make -k check"</userinput></screen>
|
|||||||
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><!--Two tests named <filename>pr104610.c</filename> and
|
<para>
|
||||||
<filename>pr69482-1.c</filename> are known to fail because the test
|
Eight gcc tests (out of over 185,000):
|
||||||
files does not account for the
|
<!-- https://gcc.gnu.org/PR106375 --><filename>pr56837.c</filename>
|
||||||
<parameter>- -enable-default-ssp</parameter> option.-->
|
and seven tests in the <filename class='directory'>analyzer</filename>
|
||||||
<!-- https://gcc.gnu.org/PR106375 and https://gcc.gnu.org/PR109353 -->
|
directory are known to fail.
|
||||||
Eight gcc tests (out of over 185,000), data-model-4.c, pr56837.c,
|
|
||||||
and six "analyzer" tests are known to fail.
|
|
||||||
|
|
||||||
One libstdc++ test (out of over 15000), copy.cc, is 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 "AddressSanitizer*"
|
For g++, 21 tests (out of approximately 250,000): 14
|
||||||
tests and 7 interception-malloc-test-1.C tests, are known to fail.
|
<quote>AddressSanitizer*</quote>
|
||||||
|
tests and 7 <filename>interception-malloc-test-1.C</filename> tests, are
|
||||||
|
known to fail.
|
||||||
|
|
||||||
Additionally, several tests in the
|
Additionally, several tests in the
|
||||||
<filename class='directory'>vect</filename> directory are known to fail
|
<filename class='directory'>vect</filename> directory are known to fail
|
||||||
if the hardware does not support AVX.</para>
|
if the hardware does not support AVX.</para>
|
||||||
<!--
|
|
||||||
<para>
|
|
||||||
With Glibc-2.39, the gcc analyzer tests named
|
|
||||||
<filename>data-model-4.c</filename> and
|
|
||||||
<filename>conftest-1.c</filename>
|
|
||||||
are known to fail.
|
|
||||||
In the asan tests, several tests in <filename>asan_test.C</filename>
|
|
||||||
are known to fail.
|
|
||||||
The test named <filename>interception-malloc-test-1.C</filename>
|
|
||||||
is known to fail.
|
|
||||||
</para>
|
|
||||||
-->
|
|
||||||
<para>A few unexpected failures cannot always be avoided. The GCC developers
|
<para>A few unexpected failures cannot always be avoided. 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.
|
||||||
Unless the test results are vastly different from those at the above URL,
|
Unless the test results are vastly different from those at the above URL,
|
||||||
it is safe to continue.</para>
|
it is safe to continue.</para>
|
||||||
|
|
||||||
<!--note><para>
|
|
||||||
On some combinations of kernel configuration and AMD processors
|
|
||||||
there may be more than 1100 failures in the gcc.target/i386/mpx
|
|
||||||
tests (which are designed to test the MPX option on recent
|
|
||||||
Intel processors). These can safely be ignored on AMD
|
|
||||||
processors. These tests will also fail on Intel processors if MPX support
|
|
||||||
is not enabled in the kernel even though it is present on the CPU.
|
|
||||||
</para></note-->
|
|
||||||
|
|
||||||
<para>Install the package:</para>
|
<para>Install the package:</para>
|
||||||
|
|
||||||
<screen><userinput remap="install">make install</userinput></screen>
|
<screen><userinput remap="install">make install</userinput></screen>
|
||||||
|
Loading…
Reference in New Issue
Block a user