public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [pushed] [gdb/testsuite] Require compilation flags in two gdb.arch/aarch64 test-cases
Date: Tue, 21 Feb 2023 15:26:41 +0100	[thread overview]
Message-ID: <20230221142641.13882-1-tdevries@suse.de> (raw)

With test-cases gdb.arch/aarch64-mte-core.exp and gdb.arch/aarch64-pauth.exp I
run into compilation errors due to unsupported compilation flags.

Fix this by requiring the compilation flags, such that I have instead:
...
UNSUPPORTED: gdb.arch/aarch64-mte-core.exp: require failed: \
  have_compile_flag -march=armv8.5-a+memtag
UNSUPPORTED: gdb.arch/aarch64-pauth.exp: require failed: \
  have_compile_flag -mbranch-protection=pac-ret+leaf
...

Tested on aarch64-linux.
---
 gdb/testsuite/gdb.arch/aarch64-mte-core.exp | 2 ++
 gdb/testsuite/gdb.arch/aarch64-pauth.exp    | 2 ++
 2 files changed, 4 insertions(+)

diff --git a/gdb/testsuite/gdb.arch/aarch64-mte-core.exp b/gdb/testsuite/gdb.arch/aarch64-mte-core.exp
index dde5df47b1a..6127ffb302b 100644
--- a/gdb/testsuite/gdb.arch/aarch64-mte-core.exp
+++ b/gdb/testsuite/gdb.arch/aarch64-mte-core.exp
@@ -166,6 +166,8 @@ proc test_mode { mode } {
 
 require is_aarch64_target
 
+require {have_compile_flag -march=armv8.5-a+memtag}
+
 # Run tests
 foreach_with_prefix mode {"sync" "async"} {
     test_mode $mode
diff --git a/gdb/testsuite/gdb.arch/aarch64-pauth.exp b/gdb/testsuite/gdb.arch/aarch64-pauth.exp
index d0dfaf96900..36d8e722072 100644
--- a/gdb/testsuite/gdb.arch/aarch64-pauth.exp
+++ b/gdb/testsuite/gdb.arch/aarch64-pauth.exp
@@ -19,6 +19,8 @@
 
 require is_aarch64_target
 
+require {have_compile_flag -mbranch-protection=pac-ret+leaf}
+
 # Build program with address signing forced on.
 standard_testfile
 set compile_flags {debug}

base-commit: 2ef339e38f51906a394105fe545058fec1f9bc4a
-- 
2.35.3


                 reply	other threads:[~2023-02-21 14:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20230221142641.13882-1-tdevries@suse.de \
    --to=tdevries@suse.de \
    --cc=gdb-patches@sourceware.org \
    /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).