From: Stephan Rohr <stephan.rohr@intel.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/1] Add functionality to disable test for specific architecture
Date: Thu, 23 Feb 2023 15:18:14 +0100 [thread overview]
Message-ID: <20230223141815.996942-1-stephan.rohr@intel.com> (raw)
From: "Rohr, Stephan" <stephan.rohr@intel.com>
Hi all,
the proposed patch adds functionality to disable a test for an architecture
as specified by the user. The current 'register_test_foreach_arch'
implementation skips all tests if the architecture is listed inside the
'skip_arch' function. However, if the user wants to skip a limited set of
tests for a given architecture, this is currently not supported by the
interface. The proposed patch extends the 'register_test_foreach_arch'
interface and allows the user to provide a set of architectures for which the
test shall not be executed, e.g.,
selftests::register_test_foreach_arch ("test_name",
function_name,
std::set<std::string> ({"arch"}));
I tested this patch with the following targets:
* unix
* unix/-m32
* native-gdbserver
* native-extended-gdbserver
No regressions are identified.
Rohr, Stephan (1):
gdb: Add functionality to disable test for specific architecture
gdb/selftest-arch.c | 11 ++++++++---
gdb/selftest-arch.h | 5 ++++-
2 files changed, 12 insertions(+), 4 deletions(-)
--
2.25.1
Intel Deutschland GmbH
Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de <http://www.intel.de>
Managing Directors: Christin Eisenschmid, Sharon Heck, Tiffany Doon Silva
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
next reply other threads:[~2023-02-23 14:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 14:18 Stephan Rohr [this message]
2023-02-23 14:18 ` [PATCH 1/1] gdb: " Stephan Rohr
2023-02-23 17:51 ` Andrew Burgess
2023-03-01 7:42 ` Rohr, Stephan
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=20230223141815.996942-1-stephan.rohr@intel.com \
--to=stephan.rohr@intel.com \
--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).