Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@palves.net>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/4] AMD GPU debugging support on Windows
Date: Fri,  8 May 2026 18:53:34 +0100	[thread overview]
Message-ID: <20260508175338.536044-1-pedro@palves.net> (raw)

To support AMD GPU debugging on Windows, we need the following pieces:

 [x] Windows non-stop support

    Merged last week.  This is needed because the amd-dbgapi-target
    target requires working in coordination with a CPU/process_stratum
    target backend that always works in non-stop mode.

 [ ] Multiple solib providers at once

    This is needed because the way we hack into solib-svr4 for the GPU
    code loader does not work on Windows, as Windows uses
    solib-target.

    This is Simon's series at
    https://inbox.sourceware.org/gdb-patches/5b5fc6b8-a0b4-4346-88e1-4974a9eed31c@polymtl.ca/T/

 [ ] Windows tweaks for amd-dbgapi-target

    This is this series.  With this, you'll be able to build a GDB
    that links against a Windows build of the AMD Debug API library,
    and activate the amd-dbgapi-target target.

Technically, we also need support for gfx1200/gfx1201 in bfd as those
are the GPUs currently supported by the Windows GPU driver for
debugging, but I consider that a separate detail.  Bfd support for
those architectures is pending at
https://inbox.sourceware.org/binutils/20251031175411.1303161-1-luis.machado@amd.com/

I'm proposing adding a NEWS entry already, as I expect Simon's series
will land soon enough, and really the upstream support for AMD GPU
debugging is very limited, just like the Linux support is, so it won't
make much of a difference in practice either way.  This will get
better when DWARF 6 is further ahead and we're able to upstream the
location-on-the-stack changes, address spaces support, and more, that
come with it, which will unlock upstreaming a lot more downstream
ROCgdb code and enable full AMD GPU debugging support directly
upstream (on both Linux and Windows).

Lancelot SIX (3):
  gdb/amd-dbgapi-target: Move Linux code to amd-dbagapi-posix-hdep.c
  gdb/amd-dbgapi-target: Add amd-dbgapi-mingw-hdep.c for Windows
  gdb/amd-dbgapi-target: Update xfer_partial to always use dbgapi

Pedro Alves (1):
  gdb/NEWS: Add note about AMD GPU debugging on Windows

 gdb/Makefile.in             |   3 +
 gdb/NEWS                    |   5 ++
 gdb/amd-dbgapi-hdep.h       |  38 ++++++++
 gdb/amd-dbgapi-mingw-hdep.c | 172 ++++++++++++++++++++++++++++++++++++
 gdb/amd-dbgapi-posix-hdep.c |  55 ++++++++++++
 gdb/amd-dbgapi-target.c     |  76 +++++++++++-----
 gdb/configure               |  13 +++
 gdb/configure.ac            |  13 +++
 8 files changed, 351 insertions(+), 24 deletions(-)
 create mode 100644 gdb/amd-dbgapi-hdep.h
 create mode 100644 gdb/amd-dbgapi-mingw-hdep.c
 create mode 100644 gdb/amd-dbgapi-posix-hdep.c


base-commit: 7a15a5f571da8772765bfb17d1049a097205035e
-- 
2.53.0


             reply	other threads:[~2026-05-08 17:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-08 17:53 Pedro Alves [this message]
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
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=20260508175338.536044-1-pedro@palves.net \
    --to=pedro@palves.net \
    --cc=gdb-patches@sourceware.org \
    /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