Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Aktemur, Baris" <TankutBaris.Aktemur@amd.com>
To: Simon Marchi <simark@simark.ca>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	"Six, Lancelot" <Lancelot.Six@amd.com>
Subject: RE: [PATCH v2] gdb, amdgpu: add config guards for AMD_DBGAPI_STATUS_ERROR_MEMORY_UNAVAILABLE
Date: Fri, 16 Oct 2026 06:52:47 +0000	[thread overview]
Message-ID: <DM4PR12MB6470591E84216B5C0B603FB7F89B2@DM4PR12MB6470.namprd12.prod.outlook.com> (raw)
In-Reply-To: <fc78be29-3a2a-4ec5-a358-d382b74cf636@simark.ca>

AMD General

On Thursday, October 15, 2026 9:04 PM, Simon Marchi wrote:
> On 10/15/26 2:15 PM, Tankut Baris Aktemur wrote:
> > diff --git a/gdb/configure.ac b/gdb/configure.ac
> > index e0117ede292..7a437747e35 100644
> > --- a/gdb/configure.ac
> > +++ b/gdb/configure.ac
> > @@ -368,6 +368,27 @@ if test "$gdb_require_amd_dbgapi" = true \
> >       AC_MSG_ERROR([amd-dbgapi not supported for host ${gdb_host}])
> >       ;;
> >      esac
> > +
> > +    # Detect if AMD_DBGAPI_STATUS_ERROR_MEMORY_UNAVAILABLE can be used.
>
> As a person who likes to clean up obsolete code, may I ask you to
> mention which dbgapi version introduced
> AMD_DBGAPI_STATUS_ERROR_MEMORY_UNAVAILABLE?  This way it will become easier
> to spot when this configure check is no longer necessary.

It became available with rocm-dbgapi-0.78.  I'll add this to the comment above.

-Baris


  reply	other threads:[~2026-10-16  6:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-15 18:15 Tankut Baris Aktemur
2026-10-15 19:03 ` Simon Marchi
2026-10-16  6:52   ` Aktemur, Baris [this message]
2026-10-19 15:00     ` Six, Lancelot

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=DM4PR12MB6470591E84216B5C0B603FB7F89B2@DM4PR12MB6470.namprd12.prod.outlook.com \
    --to=tankutbaris.aktemur@amd.com \
    --cc=Lancelot.Six@amd.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simark@simark.ca \
    /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