From: Lancelot SIX <Lancelot.Six@amd.com>
To: simon.marchi@polymtl.ca, gdb-patches@sourceware.org
Cc: Simon Marchi <simon.marchi@efficios.com>
Subject: Re: [PATCH 1/3] gdb/amd-dbgapi: use gdb::unordered_map
Date: Wed, 15 Jan 2025 10:55:26 +0000 [thread overview]
Message-ID: <dbe26a98-437b-4739-aaee-2175ba3f4ff4@amd.com> (raw)
In-Reply-To: <20250114191818.2393132-2-simon.marchi@polymtl.ca>
On 14/01/2025 19:16, simon.marchi@polymtl.ca wrote:
> Caution: This message originated from an External Source. Use proper caution when opening attachments, clicking links, or responding.
>
>
> From: Simon Marchi <simon.marchi@efficios.com>
>
> Since we have gdb::unordered_map, swap std::unordered_map for that.
>
Hi,
That looks good to me, thanks.
Since it only touches the amdgpu backend,
Approved-By: Lancelot Six <lancelot.six@amd.com> (amdgpu)
Best,
Lancelot.
> Change-Id: If2ef652fe18c1a440a25cff6131d29e37091bdbe
> ---
> gdb/amd-dbgapi-target.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/gdb/amd-dbgapi-target.c b/gdb/amd-dbgapi-target.c
> index 2bb79acd76f0..153a35f788ed 100644
> --- a/gdb/amd-dbgapi-target.c
> +++ b/gdb/amd-dbgapi-target.c
> @@ -24,6 +24,7 @@
> #include "cli/cli-cmds.h"
> #include "cli/cli-decode.h"
> #include "cli/cli-style.h"
> +#include "gdbsupport/unordered_map.h"
> #include "inf-loop.h"
> #include "inferior.h"
> #include "objfiles.h"
> @@ -207,7 +208,7 @@ struct amd_dbgapi_inferior_info
> bool enabled = false;
> } precise_memory;
>
> - std::unordered_map<decltype (amd_dbgapi_breakpoint_id_t::handle),
> + gdb::unordered_map<decltype (amd_dbgapi_breakpoint_id_t::handle),
> struct breakpoint *>
> breakpoint_map;
>
> @@ -221,7 +222,7 @@ struct amd_dbgapi_inferior_info
>
> wave_info objects are added when we first see the wave, and
> removed from a thread_deleted observer. */
> - std::unordered_map<decltype (amd_dbgapi_wave_id_t::handle), wave_info>
> + gdb::unordered_map<decltype (amd_dbgapi_wave_id_t::handle), wave_info>
> wave_info_map;
> };
>
> --
> 2.47.1
>
next prev parent reply other threads:[~2025-01-15 10:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-14 19:16 [PATCH 0/3] Add displaced stepping support for AMD GPUs simon.marchi
2025-01-14 19:16 ` [PATCH 1/3] gdb/amd-dbgapi: use gdb::unordered_map simon.marchi
2025-01-15 10:55 ` Lancelot SIX [this message]
2025-01-15 18:41 ` Simon Marchi
2025-01-15 18:46 ` Simon Marchi
2025-01-15 18:50 ` Guinevere Larsen
2025-01-15 18:55 ` Lancelot SIX
2025-01-14 19:16 ` [PATCH 2/3] gdb: add target displaced stepping support simon.marchi
2025-01-14 19:16 ` [PATCH 3/3] gdb/amd-dbgapi: add " simon.marchi
2025-01-15 11:02 ` Lancelot SIX
2025-01-15 18:45 ` Simon Marchi
2025-02-25 17:17 ` Simon Marchi
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=dbe26a98-437b-4739-aaee-2175ba3f4ff4@amd.com \
--to=lancelot.six@amd.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@efficios.com \
--cc=simon.marchi@polymtl.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