From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <pedro@palves.net>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 4/4] gdb/NEWS: Add note about AMD GPU debugging on Windows
Date: Fri, 08 May 2026 21:29:35 +0300 [thread overview]
Message-ID: <86o6ip69gw.fsf@gnu.org> (raw)
In-Reply-To: <20260508175338.536044-5-pedro@palves.net> (message from Pedro Alves on Fri, 8 May 2026 18:53:38 +0100)
> From: Pedro Alves <pedro@palves.net>
> Date: Fri, 8 May 2026 18:53:38 +0100
>
> Change-Id: I03c28920f36412c506cf18861c97483d7fabfdd5
> commit-id: 6b7fd462
> ---
> gdb/NEWS | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/gdb/NEWS b/gdb/NEWS
> index 480e1854002..68f345dd9c6 100644
> --- a/gdb/NEWS
> +++ b/gdb/NEWS
> @@ -78,6 +78,11 @@
> * The Windows native target now supports non-stop mode. This feature
> requires Windows 10 or later.
>
> +* AMD GPU ROCm debugging support on Windows
> +
> +GDB now supports debugging programs offloaded to AMD GPUs using the
> +ROCm platform, on Windows. Previously only Linux was supported.
> +
> * New targets
>
> GNU/Linux/MicroBlaze (gdbserver) microblazeel-*linux*
Thanks, this is okay.
Approved-By: Eli Zaretskii <eliz@gnu.org>
next prev parent reply other threads:[~2026-05-08 18:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 17:53 [PATCH 0/4] AMD GPU debugging support " Pedro Alves
2026-05-08 17:53 ` [PATCH 1/4] gdb/amd-dbgapi-target: Move Linux code to amd-dbagapi-posix-hdep.c Pedro Alves
2026-05-08 17:53 ` [PATCH 2/4] gdb/amd-dbgapi-target: Add amd-dbgapi-mingw-hdep.c for Windows Pedro Alves
2026-05-08 17:53 ` [PATCH 3/4] gdb/amd-dbgapi-target: Update xfer_partial to always use dbgapi Pedro Alves
2026-05-08 17:53 ` [PATCH 4/4] gdb/NEWS: Add note about AMD GPU debugging on Windows Pedro Alves
2026-05-08 18:29 ` Eli Zaretskii [this message]
2026-06-12 13:39 ` [PATCH 0/4] AMD GPU debugging support " Pedro Alves
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=86o6ip69gw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@palves.net \
/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