From: Pedro Alves <pedro@palves.net>
To: gdb-patches@sourceware.org
Cc: Lancelot SIX <Lancelot.Six@amd.com>
Subject: [PATCH 2/2] allow_hipcc_tests: Allow native Windows (windows-msvc)
Date: Mon, 10 Aug 2026 23:46:32 +0100 [thread overview]
Message-ID: <20260810224633.3455055-3-pedro@palves.net> (raw)
In-Reply-To: <20260810224633.3455055-1-pedro@palves.net>
Make allow_hipcc_tests allow Windows as well. Slightly tweak the
returned string to be more generic. Add comment about why we do the
istarget check at all.
We only allow windows-msvc, and not mingw, as the AMD ROCm compiler on
Windows targets x86_64-pc-windows-msvc.
Change-Id: I45262f2fe24455ade6075eded2cd7df03979c6cc
---
gdb/testsuite/lib/rocm.exp | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/gdb/testsuite/lib/rocm.exp b/gdb/testsuite/lib/rocm.exp
index 025fa63da6f..439870b8263 100644
--- a/gdb/testsuite/lib/rocm.exp
+++ b/gdb/testsuite/lib/rocm.exp
@@ -138,8 +138,12 @@ gdb_caching_proc allow_hip_tests {} {
return {0 "remote debugging"}
}
- if {![istarget "*-linux*"]} {
- return {0 "target platform is not Linux"}
+ # Check a hardcoded set of targets as an optimization, so that we
+ # save one external program invocation (of 'gdb --configuration')
+ # when GDB is not configured with amd-dbgapi support. External
+ # program invocations have a non-negligible time cost on Windows.
+ if {![istarget "*-linux*"] && ![istarget "*-*-windows-msvc*"]} {
+ return {0 "target platform is not supported"}
}
# Ensure that GDB is built with amd-dbgapi support.
--
2.54.0
prev parent reply other threads:[~2026-08-10 22:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-10 22:46 [PATCH 0/2] gdb/testsuite: Make ROCm/HIP tests work on native Windows Pedro Alves
2026-08-10 22:46 ` [PATCH 1/2] gdb/testsuite: For ROCm/HIP, don't rely on rocm_agent_enumerator Pedro Alves
2026-08-10 22:46 ` Pedro Alves [this message]
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=20260810224633.3455055-3-pedro@palves.net \
--to=pedro@palves.net \
--cc=Lancelot.Six@amd.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