arm64: gcc: document test failures with PIE/SSP

This commit is contained in:
Xi Ruoyao 2022-09-24 15:38:53 +08:00
parent 44784c1b8a
commit 54eb9b78da
No known key found for this signature in database
GPG Key ID: ACAAD20E19E710E3

View File

@ -156,10 +156,32 @@ su tester -c "PATH=$PATH make -k check"</userinput></screen>
url="&test-results;"/> and
<ulink url="https://gcc.gnu.org/ml/gcc-testresults/"/>.</para>
<para>In gcc, eleven tests, in the i386 test suite are known to FAIL.
It's because the test files do not account for the
<para>In gcc tests, the tests related to
<filename>fuse_adrp_add_1.c</filename>,
<filename>pr63304_1.c</filename>,
<filename>pr70120-2.c</filename>,
<filename>pr78733.c</filename>,
<filename>pr78796.c</filename>,
<filename>pr79041-2.c</filename>,
<filename>pr94530.c</filename>,
<filename>pr94577.c</filename>,
<filename>reload-valid-spoff.c</filename>, and
many <filename>aapcs64</filename> tests are known to fail.
They are because the test files do not account for the
<parameter>--enable-default-pie</parameter> option.</para>
<para>In gcc tests, the tests related to
<filename>pr104005.c</filename>,
<filename>pr103147-10.C</filename>,
<filename>shrink_wrap_1.c</filename>,
<filename>stack-check-cfa-1.c</filename>,
<filename>stack-check-cfa-2.c</filename>,
<filename>test_frame_17.c</filename>, and
many <filename>sve/pcs</filename> tests are known
to fail. The g++ test related to <filename>pr103147-10.C</filename>
is known to fail. They are because the test files do not account for
the <parameter>--enable-default-ssp</parameter> option.</para>
<para>In g++, four tests related to PR100400 are known to be reported
as both XPASS and FAIL. It's because the test file for this known issue
is not well written.</para>
@ -176,7 +198,9 @@ su tester -c "PATH=$PATH make -k check"</userinput></screen>
are known to fail.</para>
<!-- Need further investigation -->
<para>Many gcc and g++ tests related to hwasan are known to fail.</para>
<para>Many gcc and g++ tests related to hwasan are known to fail.
And, two tests related to <filename>thread_leak1.c</filename> are known
to fail for both gcc and g++.</para>
<para>A few unexpected failures cannot always be avoided. The GCC developers
are usually aware of these issues, but have not resolved them yet.