From: Tom Tromey <tom@tromey.com>
Date: Tue, 11 Mar 2025 17:20:48 +0000 (-0600)
Subject: Use gdb unordered map in linux-nat.c
X-Git-Tag: binutils-2_45~1139
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=f9868995b4b8b7f0abeaf53365181fc05e54ee1f;p=thirdparty%2Fbinutils-gdb.git

Use gdb unordered map in linux-nat.c

This changes one spot in linux-nat.c to use gdb::unordered_map.
(There are still other spots that could be converted.)

Approved-By: Simon Marchi <simon.marchi@efficios.com>
---

diff --git a/gdb/linux-tdep.c b/gdb/linux-tdep.c
index 735d20dc050..fec6a6343d7 100644
--- a/gdb/linux-tdep.c
+++ b/gdb/linux-tdep.c
@@ -44,9 +44,9 @@
 #include "solib-svr4.h"
 #include "memtag.h"
 #include "cli/cli-style.h"
+#include "gdbsupport/unordered_map.h"
 
 #include <ctype.h>
-#include <unordered_map>
 
 /* This enum represents the values that the user can choose when
    informing the Linux kernel about which memory mappings will be
@@ -1189,7 +1189,7 @@ linux_read_core_file_mappings
     warning (_("malformed note - filename area is too big"));
 
   const bfd_build_id *orig_build_id = cbfd->build_id;
-  std::unordered_map<ULONGEST, const bfd_build_id *> vma_map;
+  gdb::unordered_map<ULONGEST, const bfd_build_id *> vma_map;
 
   /* Search for solib build-ids in the core file.  Each time one is found,
      map the start vma of the corresponding elf header to the build-id.  */