From: "Vahedi, Shahab" <Shahab.Vahedi@amd.com>
To: "Machado, Luis" <Luis.Machado@amd.com>,
Simon Marchi <simark@simark.ca>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: Shahab Vahedi <list+gdb@vahedi.org>,
Simon Marchi <simon.marchi@efficios.com>,
"Six, Lancelot" <Lancelot.Six@amd.com>
Subject: Re: [PATCH] gdb.rocm/watchpoint-basic: add gfx1103 to XFAILs
Date: Mon, 10 Aug 2026 08:44:47 +0000 [thread overview]
Message-ID: <07b642f0-f2f2-4f8b-907e-b5167e181cf9@amd.com> (raw)
In-Reply-To: <SJ5PPF816B883751E2B177ADF5E2D677F589DD12@SJ5PPF816B88375.namprd12.prod.outlook.com>
On 7-Aug-2026 07:36PM, Simon Marchi wrote:
> As a subsequent comment, I wonder if, for these arches, instead of
> xfail-ing, it would be more useful to dispatch that dummy commit and
> then expect the watchpoint to work.
IMO, this would not trigger us if/when the KFD issue is resolved, so
the "list" won't go away. Having the "list" removed has the benefit
of treating any failure from that point onward as a new one.
On 7-Aug-2026 10:58PM, Machado, Luis wrote:
> I think that'd makes sense. And if we want to make sure we still expose
> the KFD issue, we could run a quick check first (but not FAIL) and
> proceed to use the workaround if needed.
What would be this quick-check (without failures)?
How would it cover new architectures?
Or is it going to "fallback" in case of "any" failure?
Yet again, how would it trigger us when the problem is resolved?
-Shahab
prev parent reply other threads:[~2026-08-10 8:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-07 16:28 Shahab Vahedi
2026-08-07 17:36 ` Simon Marchi
2026-08-07 20:58 ` Machado, Luis
2026-08-10 8:44 ` Vahedi, Shahab [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=07b642f0-f2f2-4f8b-907e-b5167e181cf9@amd.com \
--to=shahab.vahedi@amd.com \
--cc=Lancelot.Six@amd.com \
--cc=Luis.Machado@amd.com \
--cc=gdb-patches@sourceware.org \
--cc=list+gdb@vahedi.org \
--cc=simark@simark.ca \
--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