aboutsummaryrefslogtreecommitdiff
path: root/gdb/python
diff options
context:
space:
mode:
authorTom Tromey <tom@tromey.com>2025-03-11 11:22:05 -0600
committerTom Tromey <tom@tromey.com>2025-03-18 05:32:04 -0600
commitfd34c152ef22b65bc942c6d36a04a4272ef4c6fd (patch)
treeb8fce4592b95beab230456fe7e4a0a83feb69401 /gdb/python
parent7116b64e238b641fbbdf941814e4c8250b173a28 (diff)
downloadgdb-fd34c152ef22b65bc942c6d36a04a4272ef4c6fd.zip
gdb-fd34c152ef22b65bc942c6d36a04a4272ef4c6fd.tar.gz
gdb-fd34c152ef22b65bc942c6d36a04a4272ef4c6fd.tar.bz2
Use gdb unordered set and map in Python layer
This changes a couple of files in the Python layer to use gdb:unordered_set and gdb::unordered_map. Another use exists but I think it is being handled by Jan's series. Approved-By: Simon Marchi <simon.marchi@efficios.com>
Diffstat (limited to 'gdb/python')
-rw-r--r--gdb/python/py-inferior.c4
-rw-r--r--gdb/python/py-registers.c4
2 files changed, 4 insertions, 4 deletions
diff --git a/gdb/python/py-inferior.c b/gdb/python/py-inferior.c
index 60bf56d..d11ca9e 100644
--- a/gdb/python/py-inferior.c
+++ b/gdb/python/py-inferior.c
@@ -30,10 +30,10 @@
#include "py-event.h"
#include "py-stopevent.h"
#include "progspace-and-thread.h"
-#include <unordered_map>
+#include "gdbsupport/unordered_map.h"
using thread_map_t
- = std::unordered_map<thread_info *, gdbpy_ref<thread_object>>;
+ = gdb::unordered_map<thread_info *, gdbpy_ref<thread_object>>;
struct inferior_object
{
diff --git a/gdb/python/py-registers.c b/gdb/python/py-registers.c
index 229dd62..75f99e5 100644
--- a/gdb/python/py-registers.c
+++ b/gdb/python/py-registers.c
@@ -22,7 +22,7 @@
#include "reggroups.h"
#include "python-internal.h"
#include "user-regs.h"
-#include <unordered_map>
+#include "gdbsupport/unordered_map.h"
/* Per-gdbarch data type. */
typedef std::vector<gdbpy_ref<>> gdbpy_register_type;
@@ -98,7 +98,7 @@ gdbpy_get_reggroup (const reggroup *reggroup)
/* Map from GDB's internal reggroup objects to the Python representation.
GDB's reggroups are global, and are never deleted, so using a map like
this is safe. */
- static std::unordered_map<const struct reggroup *,gdbpy_ref<>>
+ static gdb::unordered_map<const struct reggroup *,gdbpy_ref<>>
gdbpy_reggroup_object_map;
/* If there is not already a suitable Python object in the map then