From: "Machado, Luis" <Luis.Machado@amd.com>
To: Simon Marchi <simark@simark.ca>,
"Vahedi, Shahab" <Shahab.Vahedi@amd.com>,
"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: Fri, 7 Aug 2026 20:58:06 +0000 [thread overview]
Message-ID: <SJ5PPF816B883751E2B177ADF5E2D677F589DD12@SJ5PPF816B88375.namprd12.prod.outlook.com> (raw)
In-Reply-To: <d7c12dad-4240-4fed-a620-2ca357ae4f79@simark.ca>
> 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.
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.
next prev parent reply other threads:[~2026-08-07 20:58 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 [this message]
2026-08-10 8:44 ` Vahedi, Shahab
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=SJ5PPF816B883751E2B177ADF5E2D677F589DD12@SJ5PPF816B88375.namprd12.prod.outlook.com \
--to=luis.machado@amd.com \
--cc=Lancelot.Six@amd.com \
--cc=Shahab.Vahedi@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