public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Xi Ruoyao <xry111@xry111.site>
To: gcc-patches@gcc.gnu.org
Cc: Richard Sandiford <richard.sandiford@arm.com>,
	Xi Ruoyao <xry111@xry111.site>
Subject: [PATCH 4/8] aarch64: testsuite: disable stack protector for sve-pcs tests
Date: Thu,  2 Mar 2023 02:07:16 +0800	[thread overview]
Message-ID: <20230301180720.26514-5-xry111@xry111.site> (raw)
In-Reply-To: <20230301180720.26514-1-xry111@xry111.site>

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


  parent reply	other threads:[~2023-03-01 18:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-01 18:07 [PATCH 0/8] aarch64: testsuite: Fix test failures with --enable-default-pie or --enable-default-ssp Xi Ruoyao
2023-03-01 18:07 ` [PATCH 1/8] aarch64: testsuite: disable PIE for aapcs64 tests [PR70150] Xi Ruoyao
2023-03-01 18:07 ` [PATCH 2/8] aarch64: testsuite: disable PIE for tests with large code model [PR70150] Xi Ruoyao
2023-03-01 18:07 ` [PATCH 3/8] aarch64: testsuite: disable PIE for fuse_adrp_add_1.c [PR70150] Xi Ruoyao
2023-03-01 18:07 ` Xi Ruoyao [this message]
2023-03-01 18:07 ` [PATCH 5/8] aarch64: testsuite: disable stack protector for pr103147-10 tests Xi Ruoyao
2023-03-01 18:07 ` [PATCH 6/8] aarch64: testsuite: disable stack protector for auto-init-7.c Xi Ruoyao
2023-03-01 18:07 ` [PATCH 7/8] aarch64: testsuite: disable stack protector for pr104005.c Xi Ruoyao
2023-03-01 18:07 ` [PATCH 8/8] aarch64: testsuite: disable stack protector for tests relying on stack offset Xi Ruoyao
2023-03-02 10:26 ` [PATCH 0/8] aarch64: testsuite: Fix test failures with --enable-default-pie or --enable-default-ssp Richard Sandiford
2023-03-07  7:43   ` Pushed: " Xi Ruoyao

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230301180720.26514-5-xry111@xry111.site \
    --to=xry111@xry111.site \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=richard.sandiford@arm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).