From: Simon Marchi <simark@simark.ca>
To: Shahab Vahedi <shahab.vahedi@amd.com>, gdb-patches@sourceware.org
Cc: Shahab Vahedi <list+gdb@vahedi.org>,
Simon Marchi <simon.marchi@efficios.com>
Subject: Re: [PATCH] gdb.rocm/watchpoint-basic: add gfx1103 to XFAILs
Date: Fri, 7 Aug 2026 13:36:13 -0400 [thread overview]
Message-ID: <d7c12dad-4240-4fed-a620-2ca357ae4f79@simark.ca> (raw)
In-Reply-To: <20260807162833.7946-1-shahab.vahedi@amd.com>
On 8/7/26 12:28 PM, Shahab Vahedi wrote:
> Again, a confirmed KFD issue. By confirmed, I mean that if a dummy
> dispatch is done first, then everything goes OK.
>
> __global__ void dummy () {}
>
> int main (...)
> {
> ...
> dummy<<<1, 1>>> ();
> /* Break after malloc. */
> kernel<<<1, 1>>> (global_ptr1, global_ptr2);
> ...
> }
If it's really the case that this arch exhibits the same problem, then
it's fine to continue with the existing pattern.
Approved-By: Simon Marchi <simon.marchi@efficios.com>
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.
Simon
next prev parent reply other threads:[~2026-08-07 17:36 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 [this message]
2026-08-07 20:58 ` Machado, Luis
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=d7c12dad-4240-4fed-a620-2ca357ae4f79@simark.ca \
--to=simark@simark.ca \
--cc=gdb-patches@sourceware.org \
--cc=list+gdb@vahedi.org \
--cc=shahab.vahedi@amd.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