From: Simon Marchi <simon.marchi@polymtl.ca>
To: Lancelot SIX <lsix@lancelotsix.com>,
Simon Marchi <simon.marchi@efficios.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v3 2/3] gdb/testsuite: add linux target check in allow_hipcc_tests
Date: Fri, 15 Sep 2023 16:18:10 -0400 [thread overview]
Message-ID: <45156e33-2ea5-4003-98fd-592f762890d5@polymtl.ca> (raw)
In-Reply-To: <20230915171955.x5azvjkeavyydjls@octopus>
On 9/15/23 13:19, Lancelot SIX via Gdb-patches wrote:
> On Fri, Sep 15, 2023 at 10:52:12AM -0400, Simon Marchi via Gdb-patches wrote:
>> ROCm / HIP tests should only run on Linux for now, existing gdb.rocm
>> tests miss such a check. Add an "istarget linux" check in
>> allow_hipcc_tests.
>>
>> Change-Id: I71f69e510a754f2fdadc32de53b923ebb9835ab5
>> ---
>> gdb/testsuite/lib/rocm.exp | 4 ++++
>> 1 file changed, 4 insertions(+)
>>
>> diff --git a/gdb/testsuite/lib/rocm.exp b/gdb/testsuite/lib/rocm.exp
>> index 98a3b308228d..791f1b403bb7 100644
>> --- a/gdb/testsuite/lib/rocm.exp
>> +++ b/gdb/testsuite/lib/rocm.exp
>> @@ -67,6 +67,10 @@ gdb_caching_proc allow_hipcc_tests {} {
>> return {0 "remote debugging"}
>> }
>>
>> + if {![istarget "*-linux*"]} {
>> + return {0 "target platform is not Linux"}
>> + }
>> +
>
> Hi,
>
> This looks good to me.
>
> As this is a rocm-specific part, I think I can now add:
> Approved-By: Lancelot Six <lancelot.six@amd.com>
Indeed, thanks!
Simon
next prev parent reply other threads:[~2023-09-15 20:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-15 14:52 [PATCH v3 1/3] gdb: add inferior_cloned observable Simon Marchi
2023-09-15 14:52 ` [PATCH v3 2/3] gdb/testsuite: add linux target check in allow_hipcc_tests Simon Marchi
2023-09-15 17:19 ` Lancelot SIX
2023-09-15 20:18 ` Simon Marchi [this message]
2023-09-15 14:52 ` [PATCH v3 3/3] gdb/amdgpu: add precise-memory support Simon Marchi
2023-09-15 16:04 ` Lancelot SIX
2023-09-15 16:29 ` Simon Marchi
2023-09-15 17:16 ` Lancelot SIX
2023-09-15 20:19 ` Simon Marchi
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=45156e33-2ea5-4003-98fd-592f762890d5@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb-patches@sourceware.org \
--cc=lsix@lancelotsix.com \
--cc=simon.marchi@efficios.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).