If GCC is configured with --enable-default-ssp, the stack protector can make many sve-pcs tests fail.
gcc/testsuite/ChangeLog: * gcc.target/aarch64/sve/pcs/aarch64-sve-pcs.exp (sve_flags): Add -fno-stack-protector. --- .../gcc.target/aarch64/sve/pcs/aarch64-sve-pcs.exp | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/gcc/testsuite/gcc.target/aarch64/sve/pcs/aarch64-sve-pcs.exp b/gcc/testsuite/gcc.target/aarch64/sve/pcs/aarch64-sve-pcs.exp index 5562502cc07..3dbf73f67c9 100644 --- a/gcc/testsuite/gcc.target/aarch64/sve/pcs/aarch64-sve-pcs.exp +++ b/gcc/testsuite/gcc.target/aarch64/sve/pcs/aarch64-sve-pcs.exp @@ -37,11 +37,12 @@ if ![info exists DEFAULT_CFLAGS] then { # Initialize `dg'. dg-init -# Force SVE if we're not testing it already. +# Force SVE if we're not testing it already. And, disable stack protector +# to avoid test failures with --enable-default-ssp. if { [check_effective_target_aarch64_sve] } { - set sve_flags "" + set sve_flags "-fno-stack-protector" } else { - set sve_flags "-march=armv8.2-a+sve" + set sve_flags "-march=armv8.2-a+sve -fno-stack-protector" } # Main loop. -- 2.39.2